M
medu
Guest
Think I just said the pursue shouldn't be in throwing an error to enforce the rule... this is just an explanation on why things works as they do now, not the slightest attempt to find a solution 
Also mentioned 'strict' in sax-writer because that also gives one the possibility to build an invalid XML document, this is in no way any different... a simple strict property can be added to SOAP-HEADER and if not set then that namespace-aware restriction can be lifted, let the other end or the developer deal with it. The main idea is yes, we know they don't follow standards but you can't just go ahead and tell everyone to fix their system just because you need to integrate as long as they are doing with the rest of the world already... no one will change their system because of that.
Continue reading...
Also mentioned 'strict' in sax-writer because that also gives one the possibility to build an invalid XML document, this is in no way any different... a simple strict property can be added to SOAP-HEADER and if not set then that namespace-aware restriction can be lifted, let the other end or the developer deal with it. The main idea is yes, we know they don't follow standards but you can't just go ahead and tell everyone to fix their system just because you need to integrate as long as they are doing with the rest of the world already... no one will change their system because of that.Continue reading...