the protocol SOAP itself is not backward compatible. A SOAP implementation/engine (e.g. Axis) may be so.
The SOAP versions can be detected by means of the namespace of the Envelope of the received SOAP message.
I have no idea, why your server behaves the way it does. Sorry for that.
cheers, Christoph
J�rgen Austvik wrote:
On Tue, 2004-01-13 at 17:44, Christoph Tratter wrote:
Hi J�rgen,
The problem is, where you like it to have.
In SOAP versioning is accomplished by means of the namespace name for the SOAP envelope.
In your case the Axis client (presumably you have version 1.1 final of Axis) uses Version 1.1 of SOAP as default. This can be seen from the use of the namespace name "http://schemas.xmlsoap.org/soap/envelope/"; for the SOAP message.
On server-side you have SOAP::Lite.
This uses the namespace name "http://www.w3.org/2001/06/soap-envelope";. As far as I see it, this is the Working Draft for SOAP 1.2 from July 9 2001.
So the client "speaks" SOAP 1.1 whereas the server wants to "speak" SOAP 1.2.
It should be clear, that they do not understand each other. The SOAP specification says, that a not supported version (i.e. namespace) must result in the reponse (Fault) you get.
Oh, I imagined that SOAP was backwards compatible between minor versions.
The strange thing is that it works between the same server and client for a month with the same calls, and often the same parameters to the calls. Then it stops to work until we restart the server. Shouldn't this version-incompatiblity make it fail every time?
