[SWS-485] xml:lang="en" attribute in <faultstring> element is not compliant to SOAP/1.1 schema Created: 12/Feb/09 Updated: 04/May/12 Resolved: 13/May/09
|Project:||Spring Web Services|
|Reporter:||Oleksandr Alesinskyy||Assignee:||Arjen Poutsma|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
There is xml:lang="en" attribute in <faultstring> element although SOAP/1.1 schema doesn't provide it.
Probably, it may as well be avoided by subclassing of each of above mentioned classes (and likely some others),
IMHO, or it should comply with schema by default, or, in the worst case, it should exist some global setting
|Comment by Arjen Poutsma [ 12/Feb/09 ]|
In fact, the xml:lang element is valid. See http://www.ws-i.org/Profiles/BasicProfile-1.1.html#SOAP_Fault_Language
|Comment by Oleksandr Alesinskyy [ 12/Feb/09 ]|
O dare to disagree - official definition of SOAP schema is here http://schemas.xmlsoap.org/soap/envelope/ (as stated at http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383507) and it does not contain lang attribute for faultstring element.
I can only guess why WS-I provided non-compliant profile, likely due to many violations "in the field", but I doubt that it has right to change definitions of W3C.
Anyway, it is a valid reason to not change defaults, but not valid reason to blantantly decline providing of some kind of "global switch" between strict (W3C) and relaxed (WS-I) compliance.
I would say that client better follow WS-I but servers (with unlimited circle of clients, as in our case) should follows more strict restrictions of W3C.
|Comment by Arjen Poutsma [ 17/Feb/09 ]|
Ok, we will take a look at this for 1.5.7.
|Comment by Arjen Poutsma [ 13/May/09 ]|
I've added the langAttributeOnSoap11FaulString property to both the SaajSoapMessageFactory, and AxiomSoapMessageFactory, which defaults to true. If set to false, the xml:lang attribute will not be added to SOAP 1.1 faults.
|Comment by Arjen Poutsma [ 04/May/12 ]|
Closing old issues