M
medu
Guest
true, problem is telling this to the other end usually doesn't help and we have to come-up with solutions in order to consume all those 'standard' web-services 
we had a similar issue with a wsdl using iso-8859 encoding while Progress only supports utf-8, utf-16 ( knowledgebase.progress.com/.../P97707 )... requesting the 3-rd party to change their service is not a resolution though. in this particular case no error seems to be raised if a non namespace-aware node is attached to the soap-header reference, the reference is valid, the attached node looks valid but serialization is null... this is not to say you should enforce that by throwing an error, it should be an easy fix to accept those nodes and leave the 'wrong' message get sent to the other end (let them validate the specifications) - something like the 'strict' attribute for sax 
Continue reading...
we had a similar issue with a wsdl using iso-8859 encoding while Progress only supports utf-8, utf-16 ( knowledgebase.progress.com/.../P97707 )... requesting the 3-rd party to change their service is not a resolution though. in this particular case no error seems to be raised if a non namespace-aware node is attached to the soap-header reference, the reference is valid, the attached node looks valid but serialization is null... this is not to say you should enforce that by throwing an error, it should be an easy fix to accept those nodes and leave the 'wrong' message get sent to the other end (let them validate the specifications) - something like the 'strict' attribute for sax Continue reading...