Re: [ebxmlms-develop] JMSMessageListener contrib?

[Ronald v. K. <rv...@ab...>]

Peter mentioned in previous messages about the JMS listerner that there 
still is http-tunneling involved in his implementation. Looking at the 
code of the MessageListener and the Request implementation, I see that 
this tunneling is the only 'easy' option. I'm thinking however about a 
more direct delivery of messages through JMS. To achieve this, a lot of 
the servlet implementation has to change. Since I've read that some 
redesign things are going on (like a separate persistence layer, and 
some monitoring/controling redesign), is there a change that there will 
be changes in the way messages can be delivered?

Ronald

Ronald van Kuijk wrote:

> Hi all,
>
> Several months ago, there was a discussion about a JMSReceiver with 
> uri/url issue. Especially Peter Mayne was working on this and had a 
> working implementation for this.
>
> I'm currently working on an application that will be running within 
> the same applicationserver as Hermes. I therefor like to have a more 
> closely integrated method for sending and receiving messages. I was 
> thinking of a jms queue between the stub and hermes instead of http. 
> Is there already some code to start with, or extend? Maybe a kind of 
> contrib thing? Where I can also my LDAPURLResolver, and upcomming 
> LDAPCertResolver.
>
> Ronald
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Perforce Software.
> Perforce is the Fast Software Configuration Management System offering
> advanced branching capabilities and atomic changes on 50+ platforms.
> Free Eval! http://www.perforce.com/perforce/loadprog.html
> _______________________________________________
> ebxmlms-develop mailing list
> ebx...@li...
> https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop