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
<<winmail.dat>>
