Re: [ebxmlms-develop] JMS receiver

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

<!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>
Sorry I know nothing about JMS.. Are there any URL for JMS destinations? 
I agree that the MessageServiceHandlerConfig (and thus the mechanism of
MessageListener) should be modified. The current implementation is not
that flexible. Do you have any idea on how the architecture should be? 
 
In the meantime, an adhoc solution is to implement JMS clients with
"tunnelling" through HTTP clients, or "tunnelling" through in-process
clients.&nbsp; :-) 
 
Regards, -Patrick 
 
 
Mayne, Peter wrote: 
<blockquote type="cite"
 cite="mid...@s-...">
 <meta http-equiv="Content-Type" content="text/html; ">
 <meta name="Generator"
 content="MS Exchange Server version 5.5.2654.45">
 <title>RE: [ebxmlms-develop] JMS receiver</title>
 Yes, but what about the details? 
 Ideally, the MessageListener interface would allow
anything to be plugged into it. However, it is constrained by having to
use a URL, which obviously isn't suited for plugins such as JMS. The
use of MessageListener.getClientUrl()&nbsp; isn't numerous throughout
Hermes, but the idea that a MessageListener has a URL (which may be
null), and that URL's scheme is one of "http", "https", or "smtp", is
fairly embedded. This precludes using an alternative plugin for JMS,
FTP, etc.
 For instance, the MessageServiceHandlerConfig
constructor has a transportType parameter (I'm not sure why, I would
have thought the transport type was implicit in the MessageListener),
which must be one of the above schemes. There is no allowance for
anything else.
 Providing for different MessageListeners might be
more difficult than it looks. 
 PJDM 
 -- 
 Peter Mayne 
 Technology Consultant 
 Spherion Technology Solutions 
 Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602 
 T: 61 2 62689727&nbsp; F: 61 2 62689777 
 
 <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>
</body>
</html>