The official SOAP specification provides a standard binding for how to communicate SOAP messages over Http. This is the reason that different SOAP over Http providers can expect to interoperate; because there is a defined standard on how to do things.
Further, it is my understanding that there is no official standard binding for how to do SOAP over JMS. This means if that any two parties develop there own mechanism for doing SOAP over JMS, there is no reason to expect these two different implementations to interoperate. In fact, one should expect that they would NOT interoperate.
More specifically, if a company was to independantly come up with a mechanism for doing SOAP over JMS, they should expect that it would not interoperate with the Axis implementation of doing SOAP over JMS.
Can someone knowledgable in this area please confirm whether the above is correct? And if it is not correct, where have I gone amiss?
Thanks, Mike
_________________________________________________________________
Get fast, reliable access with MSN 9 Dial-up. Click here for Special Offer! http://click.atdmt.com/AVE/go/onm00200361ave/direct/01/
