Hi Thierry, 1. You'll need a connector and connection factory property map when you create the JMSTransport. There aren't too many options right now. Take a look at SimpleJMSListener (createConnectorMap, createCFMap) for an idea of what you can pass in.
Recently, we enhanced the JMS transport so that you could provide configuration properties in the endpoint URL itself. This would be one way to avoid the command line/property maps. Please take a look in samples/jms/dii and samples/jms/stub for examples of this. 2. That's correct (queue or topic name) 3. Unfortunately there isn't much documentation other than what you see in the source. Briefly: - JMSConnector simplifies the task of connecting to JMS destinations by encapsulating session management, retry logic, etc. It is extended by Queue/TopicConnector for PTP/PubSub support. - JMSEndpoint provides a domain-neutral means for interacting with JMS destinations. QueueConnector and TopicConnector use JMSEndpoint (or rather, domain-specific subclasses of JMSEndpoint) to send and receive messages from Queues and Topics, respectively. 4. Axis does not yet support asynchronous message invocation. However, a proposal has been submitted to address this (see /proposals/async_sonic/AxisAsyncClientAPI.htm). Thanks, Ray Chun Sonic Software -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 29, 2003 3:09 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: Configure services for JMS listener Hi Ray, Thanks for your response. My problem wasn't to configure services with wsdd, but how the jms listner knows the server-config.wsdd to use. My question was not clear enough, I think... I think I have found a response in forum: -Daxis.ServerConfigFile=path-to-server-config/server-config.wsdd I have a lot of questions about SOAP over JMS with Axis. Perhaps could you help me? 1°) How to configure ( on the client side ) the JMSTransport class. I see in jms examples, that it is with the params of the command line, but wihtout command line... 2°) Use of the destination of the Call object. I think it is the name of the queue to send message. Am I right? call.setProperty(JMSConstants.DESTINATION, "JMS_RequestQueue"); 3°) Is there documentation about JMSConnector / JMSConnectorFactory and JMSEndpoint and what are the use of these classes? 4°) Is it possible ( for the client ) to make asynchronous call? If true, how can I configure the client to receive the response? Thanks by advance for your help. Thierry > Hi Thierry, > > The JMS sample includes a server-config.wsdd file which you can > modify to invoke other services. There's nothing JMS-specific in our > service invocation code (see SimpleJMSListener/Worker), so > you should be able to follow the instructions found in the > 'Custom Deployment - Introducing WSDD' section of the user guide: > http://ws.apache.org/axis/java/user-guide.html. Please let me know > if the docs are insufficient. > > Thanks, > > Ray Chun > Sonic Software Les informations contenues dans ce message sont confidentielles et peuvent constituer des informations privilegiees. Si vous n etes pas le destinataire de ce message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d en utiliser tout ou partie. Si vous avez recu ce message par erreur, merci de le supprimer de votre systeme, ainsi que toutes ses copies, et d en avertir immediatement l expediteur par message de retour. Il est impossible de garantir que les communications par messagerie electronique arrivent en temps utile, sont securisees ou denuees de toute erreur ou virus. En consequence, l expediteur n accepte aucune responsabilite du fait des erreurs ou omissions qui pourraient en resulter. --- ----------------------------------------------------- --- The information contained in this e-mail is confidential. It may also be legally privileged. If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return e-mail. E-mail communications cannot be guaranteed to be timely secure, error or virus-free. The sender does not accept liability for any errors or omissions which arise as a result.
