Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Invalid
-
Version 2, Version 2.1, Version 2.2, Version 2.2.1, Version 2.3, Version 2.3.1, Version 2.4 , Version 2.4.1
-
None
-
None
-
None
Description
The issue here is that XMLBeans' XmlTokenSource#newXMLStreamReader(XmlOptions) doesn't take into account the XmlOptions#setSaveAggressiveNamespaces() setting (in contrast to the save methods). Therefore this is not an Axiom bug. As a workaround for this XMLBeans issue, I suggest to use XmlTokenSource#save(ContentHandler, LexicalHandler, XmlOptions) in conjunction with Axiom's SAXOMBuilder:
Attachments
Issue Links
- is related to
-
XMLBEANS-370 Namespace verbosity when serialized with AXIOM API
- Resolved