RE: Using JMS

[Ray Chun]

Title: Using JMS

Hi Peter,   We’re in the process of enhancing the JMS transport layer to support a JMS URL syntax, which will allow you to use the wsdl2java-generated stub classes without modification. With JMS URL support, Axis will recognize a JMS endpoint address and automatically register and configure the JMS transport using information in the JMS URL.    The JMS URL proposal which Dave Chappell submitted to Axis will give you a better idea of what we’re trying to do: http://marc.theaimsgroup.com/?l=axis-dev&m=105613809524476&w=2   We’re planning to commit the changes in the next week or two.  Along with that submission will be an update to the JMS samples doc which will provide more details on using JMS in Axis.   If you have any questions which you’d like to see addressed in the doc, please let me know, thanks,   Ray     -----Original Message----- From: Mayne, Peter [mailto:[EMAIL PROTECTED] Sent: Thursday, August 21, 2003 11:04 PM To: '[EMAIL PROTECTED]' Subject: Using JMS   I'm using Axis with JMS: no web/HTTP involved at all. However, everything seems to revolve around HTTP, with JMS being a very poor cousin. In particular, the classes generated by WSDL2Java provide no capability to configure the JMSTransport. Yes, I can hack xSoapBindingStub, but it's a pain to do every time. The org.apache.axis.Call class appears to have support for adding custom protocols, but "jms" isn't one of the default transports, for some reason. Is there something like a "best practices" document for using JMS with Axis? Thanks. PJDM -- Peter Mayne Technology Consultant Spherion Technology Solutions Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602 T: 61 2 62689727  F: 61 2 62689777 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.