Hi Brian, This is the code that i used at the JMS client side,
Call call = (org.apache.axis.client.Call) service.createCall(); call.setProperty(JMSConstants.DESTINATION, "queue/AXIS"); call.setProperty(JMSConstants.WAIT_FOR_RESPONSE, Boolean.FALSE); call.setTransport(transport); Instead of setting target end point on HTTP protocol, use setProperty() to set the queue name that your client will send the message to. > Oliver, > > When invoking a http service the client creates and endPoint and using > this sets the TargetEndpoint on the client.Call object. The endpoint I > was using previously was; > <http:// :8080/axis/services/serviceName> > http://localhost:8080/axis/services/serviceName > > Obviously this won't work with JMS. What format should the endPoint be > for JMS, or should I be creatingthe client.Call object competely > differently ? > > > Thanks, > > > Brian > > > -----Original Message----- > From: Oliver Adler [mailto:[EMAIL PROTECTED] > Sent: 06 March 2003 09:01 > To: [EMAIL PROTECTED] > Subject: AW: SOAP over JMS Deploying Services > > > Hi Brian, > it depends if you use document style services or rpc style. > For document style services is no common way to specify the service to > which axis should dispatch the message. The doc says that a handler > (transport specific like the urlmapper for http) has to call the > setTargetService method on the messageContext object. > For JMS there are two ways: > we use a soap header to specifiy the service and a tansport specific > handler which extracts the servicename from the header and calls the > setTargetService method. > The second one is to use jms specific header fields. > > But both ways are not standards ! The soap spec say it's up to the > application. > > For rpc its straight forward (the namespace of the first body element > specifies the service). Have a look into the URLMapper. > > Regards > > Oliver > > > ____________________________________________________________________ > > Oliver Adler, Senior Consultant > SYRACOM Systems AG - "The IT-Architects" > > Otto-von-Guericke-Ring 15 > D-65205 Wiesbaden > > Tel +49 6122-9176-0 > Fax +49 6122-9176-11 > Mobil +49 175-1853998 > > E-Mail: [EMAIL PROTECTED] > <www.SYRACOM.de> > > Ein Unternehmen der SYRACOM Gruppe - "The Business- & IT-Architects" > > ____________________________________________________________________ > > -----Ursprüngliche Nachricht----- > Von: Brian Dillon (ext. 944) [mailto:[EMAIL PROTECTED] > Gesendet: Do 06.03.2003 9.43 Uhr > An: '[EMAIL PROTECTED]' > Cc: > Betreff: SOAP over JMS Deploying Services > > > Hi, > > In order to get a SOAP service working with JMS I need to create a JMS > listener which initialises an AxisServer and then calls invoke witht > the JMS message wrapped in an Axis message. Is this correct ? How do I > then deploy a SOAP service so that this AxisServer knows where to route > the message to ? With HTTP soap services I call "axis.AdminClient > deploy ..." and the server-config.wsdd is updated (via the axis > servlet). Is there an equivalent for deploying SOAP servies over JMS ? > > Thanks, > > Brian > > > > > ************************************************************************** > The information contained in this e-mail is confidential, > may be privileged and is intended only for the use of the > recipient named above. If you are not the intended > recipient or a representative of the intended recipient, > you have received this e-mail in error and must not copy, > use or disclose the contents of this email to anybody > else. If you have received this e-mail in error, please > notify the sender immediately by return e-mail and > permanently delete the copy you received. This email has > been swept for computer viruses. However, you should > carry out your own virus checks. > > > Registered in Ireland, No. 205721. http://www.FINEOS.com > **************************************************************************
