OMSerializerUtil serializes attributes with NULL names
------------------------------------------------------
Key: WSCOMMONS-151
URL: https://issues.apache.org/jira/browse/WSCOMMONS-151
Project: WS-Commons
Issue Type: Improvement
Components: AXIOM
Environment: spring-ws-1.0-m2, axiom-1.2.2
Reporter: Petri Reiman
Currently it is possible to add OMAttributes to OMElementImpl where
OMAttributeImpl.localName value is null. This results in OMSerializer output of
form <ns:element ="value"/> where the attribute value is missing and the
resulting document is invalid.
These kind of attributes should not be added by the client code in the first
place, but should't we safeguard against this either by
1) Ignoring attributes with no serializable name when serializing ( at the end
of OMSerializerUtil.serializeStartpart where attributes are written)
2) Prevent adding malforned attributes - this would help catching errors on the
client side
We got this error while implementing document based service with spring-ws.
First element of the return message body had a namespace declaration with no
attribute name.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
