SOAP namespace soapenv vs soap-env
Please forgive the corsspost but I received no joy in the XML forum.
I've had a SOAP messaging system which has been humming along nicely for a couple of years. The recent DST change prompted me to upgrade the JRE to 1.3.1_19 (I know it's old but it was working). The system started failing. Some debugging found that some of my messages had my expected namespace of
<soap-env.....
BUT some had
><soapenv....
The system sends messages for some legacy systems. The part of the system which failed read the incoming data from a socket and searched for the ><soap-env. If this was present the message was handled one way. Not present it was handled a different way. The namespace changing caused this fragile system to break. OK that's been handled but what I need to know is why this happened. Here are some "facts" that I believe to be true....
The SOAP related jars were not updated when the JRE was updated.
The messages are failing are being generated by this machine (not from the outside world).
Any thoughts would be incredibly helpful.
Thanks as always
ST>
[1150 byte] By [
souLTowera] at [2007-11-26 23:43:59]
> some of my messages had my expected namespace of
>
> <soap-env.....
>
> BUT some had
>
> <soapenv....
Neither of these are namespaces. They're namespace prefixes, and refer to an xmlns: attribute defined on the element or one of its containers (normally on the Envelope element).
The real SOAP envelope namespace is http://www.w3.org/2003/05/soap-envelope
> The part of the system which failed read the
> incoming data from a socket and searched for the
> <soap-env.
Then you have a bug in your code and need to fix it. A valid SOAP message could have "fooledyou" for its envelope prefix. As long as that prefix is associated with the correct SOAP namespace, it's a valid SOAP message.>
Thank you. You are correct on all points. Let me re frame my question then.
For 2 years there has not been a failure looking for the
<soap-env
namespace prefix in the incoming data. Admittedly this was a bad approach and has been corrected. The question is how / why did this change. Here is an example of the expected and bad data that I'm receiving:
Expected format:
><soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"><soap-env:Header>
Bad format:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Header> <Address To="xx.xx.xxx.xx" From="xx.xx.xx.xxx" soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0" xmlns=""/>?
Thanks for the reply.
ST
Possibly I don't understand the SOAP implementation. I'm using the same set of SOAP jars (saaj, commons, logging, etc) as I always did. If these jars did not change could / should the message format change? Is the implementation looking outside of my JVM for this implementation?
As to "why" it matters is that I need to know why something in my code has changed. Imagine, for example, that the implementation of String changed. It may still adhere to the normal implementation of String but if my code expects it to look a certain way and it stops looking that way then my code breaks.
As I said in the original post I have handled the issue that it changed but I can't feel comfortable with the application if I fear that it can change again and break my code.
The question is, if the jars related to SOAP (the normal ones you get from sun, I'll provide the list if needed) have not changed then how can the format of the message change?
Thanks again.
ST
