SOAP over JMS with Attachments - How do we specify the targetService?

[Rajal Shah]

How do I set the targetService when doing SOAP/JMS with Attachments? I’ve use the call.setTargetEndPointAddress(http://localhost..) – note the http even though I’m using the jms transport but it doesn’t seem to work..   faultString: The AXIS engine could not find a target service to invoke!  targetService is null   -- Rajal   From: Rajal Shah [mailto:[EMAIL PROTECTED] Sent: Friday, November 19, 2004 1:36 PM To: [EMAIL PROTECTED] Subject: (SOAP/JMS) Why is a JMSListener not added by default to the AxisServlet?   I’ve gone through the past discussion about SOAP/JMS and haven’t found a clear roadmap on how to do SOAP/JMS by a Service Provider..   I’ve used the samples/jms/JMSTest.java file and have coded up a default JMSListener to the AxisServlet’s init() method. My web services can now be accessed through HTTP using the regular means *and* also through a jms queue.   My questions are: It really is simple to do this, if you understand the samples/jms/JMSTest example. So why is it not included to the AxisServlet engine by default and automatically have both the JMS and HTTP listeners working on the same Axis engine? From the previous threads, people have talked about using the WSDL and JMSTransport directly to publish the web service to do SOAP/JMS.. Is it really possible? Can some Axis guru provide us more info/sample code for it? Can we write a WSDL which can publish the web services to have have both the HTTP and JMS transport layers?   Regards. -- Rajal