As to your questions 2nd and 3rd, Yes it is possible to have webservices over different protocols, meaning we can publish a webservice which can work on top of different protocols like SOAP, RMI-IIOP protocol all simultaneously. This has been possible 'cause wsdl allows for a definition of a webservice having multiple bindings(which can be soap, ejb etc). There's a framework which caters to these stuffs..I'm giving a link below, I guess it would provide you with answers.
http://www-106.ibm.com/developerworks/library/ws-wsif.html Cheers Vinay On Fri, 19 Nov 2004 13:36:10 -0800, Rajal Shah <[EMAIL PROTECTED]> wrote: > > > > 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 > > > >
