|
From: Patrick Y. <kc...@ce...> - 2004-01-14 09:43:52
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"> <title></title> </head> <body text="#000000" bgcolor="#ffffff"> Peter and Ronald,<br> <br> Do you think it is possible to base the generic listener on the JMS one done by Peter? If so, I would like to invite Peter to coordinate with Ronald on this. I guess the work flow is as follows: we need to align the design first, and then make the code done and then finally post it to the CVS. What do you think?<br> <br> Regards, -Patrick<br> <br> <br> Mayne, Peter wrote:<br> <blockquote type="cite" cite="mid...@s-..."> <meta content="text/html; " http-equiv="Content-Type"> <meta content="MS Exchange Server version 5.5.2654.45" name="Generator"> <title>RE: [ebxmlms-develop] JMSMessageListener contrib?</title> <p><font size="2">Ronald is correct: I'm still using an HTTP listener which just passes the message to JMS.</font> </p> <p><font size="2">I did go some way to using JMS directly, but the current implementation isn't completely broken, so I didn't completely fix it. :-)</font></p> <p><font size="2">I would also like to see a more generic listener in Hermes.</font> </p> <p><font size="2">PJDM</font> <br> <font size="2">-- </font> <br> <font size="2">Peter Mayne</font> <br> <font size="2">Technology Consultant</font> <br> <font size="2">Spherion Technology Solutions</font> <br> <font size="2">Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602</font> <br> <font size="2">T: 61 2 62689727 F: 61 2 62689777</font> </p> <p><font size="2">> -----Original Message-----</font> <br> <font size="2">> From: Ronald van Kuijk [<a href="mailto:rv...@ab...">mailto:rv...@ab...</a>] </font> <br> <font size="2">> Sent: Monday, 12 January 2004 12:24 AM</font> <br> <font size="2">> To: <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a></font> <br> <font size="2">> Subject: Re: [ebxmlms-develop] JMSMessageListener contrib?</font> <br> <font size="2">> </font> <br> <font size="2">> </font> <br> <font size="2">> Peter mentioned in previous messages about the JMS listerner </font> <br> <font size="2">> that there </font> <br> <font size="2">> still is http-tunneling involved in his implementation. </font> <br> <font size="2">> Looking at the </font> <br> <font size="2">> code of the MessageListener and the Request implementation, I </font> <br> <font size="2">> see that </font> <br> <font size="2">> this tunneling is the only 'easy' option. I'm thinking </font> <br> <font size="2">> however about a </font> <br> <font size="2">> more direct delivery of messages through JMS. To achieve </font> <br> <font size="2">> this, a lot of </font> <br> <font size="2">> the servlet implementation has to change. Since I've read that some </font> <br> <font size="2">> redesign things are going on (like a separate persistence layer, and </font> <br> <font size="2">> some monitoring/controling redesign), is there a change that </font> <br> <font size="2">> there will </font> <br> <font size="2">> be changes in the way messages can be delivered?</font> <br> <font size="2">> </font> <br> <font size="2">> Ronald</font> <br> <font size="2">> </font> <br> <font size="2">> Ronald van Kuijk wrote:</font> <br> <font size="2">> </font> <br> <font size="2">> > Hi all,</font> <br> <font size="2">> ></font> <br> <font size="2">> > Several months ago, there was a discussion about a JMSReceiver with </font> <br> <font size="2">> > uri/url issue. Especially Peter Mayne was working on this and had a </font> <br> <font size="2">> > working implementation for this.</font> <br> <font size="2">> ></font> <br> <font size="2">> > I'm currently working on an application that will be running within </font> <br> <font size="2">> > the same applicationserver as Hermes. I therefor like to </font> <br> <font size="2">> have a more </font> <br> <font size="2">> > closely integrated method for sending and receiving messages. I was </font> <br> <font size="2">> > thinking of a jms queue between the stub and hermes instead </font> <br> <font size="2">> of http. </font> <br> <font size="2">> > Is there already some code to start with, or extend? Maybe </font> <br> <font size="2">> a kind of </font> <br> <font size="2">> > contrib thing? Where I can also my LDAPURLResolver, and upcomming </font> <br> <font size="2">> > LDAPCertResolver.</font> <br> <font size="2">> ></font> <br> <font size="2">> > Ronald</font> <br> <font size="2">> ></font> <br> <font size="2">> ></font> <br> <font size="2">> > -------------------------------------------------------</font> <br> <font size="2">> > This SF.net email is sponsored by: Perforce Software.</font> <br> <font size="2">> > Perforce is the Fast Software Configuration Management </font> <br> <font size="2">> System offering</font> <br> <font size="2">> > advanced branching capabilities and atomic changes on 50+ platforms.</font> <br> <font size="2">> > Free Eval! <a target="_blank" href="http://www.perforce.com/perforce/loadprog.html">http://www.perforce.com/perforce/loadprog.html</a></font> <br> <font size="2">> > _______________________________________________</font> <br> <font size="2">> > ebxmlms-develop mailing list</font> <br> <font size="2">> > <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a></font> <br> <font size="2">> > <a target="_blank" href="https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop">https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop</a></font> <br> <font size="2">> </font> <br> <font size="2">> </font> <br> <font size="2">> </font> <br> <font size="2">> </font> <br> <font size="2">> -------------------------------------------------------</font> <br> <font size="2">> This SF.net email is sponsored by: Perforce Software.</font> <br> <font size="2">> Perforce is the Fast Software Configuration Management System offering</font> <br> <font size="2">> advanced branching capabilities and atomic changes on 50+ platforms.</font> <br> <font size="2">> Free Eval! <a target="_blank" href="http://www.perforce.com/perforce/loadprog.html">http://www.perforce.com/perforce/loadprog.html</a></font> <br> <font size="2">> _______________________________________________</font> <br> <font size="2">> ebxmlms-develop mailing list</font> <br> <font size="2">> <a class="moz-txt-link-abbreviated" href="mailto:ebx...@li...">ebx...@li...</a></font> <br> <font size="2">> <a target="_blank" href="https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop">https://lists.sourceforge.net/lists/listinfo/ebxmlms-develop</a></font> <br> <font size="2">> </font> </p> <font color="BLUE" size="3"> <pre>The information contained in this email and any attachments to it: (a) may be confidential and if you are not the intended recipient, any interference with, use, disclosure or copying of this material is unauthorised and prohibited; and (b) may contain personal information of the recipient and/or the sender as defined under the Privacy Act 1988 (Cth). Consent is hereby given by the recipient(s) to collect, hold and use such information and any personal information contained in a response to this email, for any reasonable purpose in the ordinary course of Spherion's business, including forwarding this email internally or disclosing it to a third party. All personal information collected by Spherion will be handled in accordance with Spherion's Privacy Policy. If you have received this email in error, please notify the sender and delete it. (c) you agree not to employ or arrange employment for any candidate(s) supplied in this email and any attachments without first entering into a contractual agreement with Spherion. You further agree not to divulge any information contained in this document to any person(s) or entities without the express permission of Spherion. </pre> </font></blockquote> <br> </body> </html> |