[
https://issues.jboss.org/browse/JBXB-194?page=com.atlassian.jira.plugin.s...
]
Fernando Ribeiro edited comment on JBXB-194 at 8/29/13 4:20 PM:
----------------------------------------------------------------
<xs:complexType name="detail">
<xs:sequence>
<xs:any namespace="##any" minOccurs="0"
maxOccurs="unbounded" processContents="lax" />
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax" />
</xs:complexType>
was (Author: fribeiro1):
I've confirmed today that the element in question isn't mixed:
<xs:complexType name="detail">
<xs:sequence>
<xs:any namespace="##any" minOccurs="0"
maxOccurs="unbounded" processContents="lax" />
</xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax" />
</xs:complexType>
I'll run a new test until tomorrow to try to learn some more.
Support for Ignoring Whitespace-Only Nodes
------------------------------------------
Key: JBXB-194
URL:
https://issues.jboss.org/browse/JBXB-194
Project: JBoss XML Binding (JBossXB)
Issue Type: Feature Request
Affects Versions: JBossXB-1.0.0.SP3
Reporter: Fernando Ribeiro
While accessing the detail of SOAP faults with JBossWS 3.0.1, I've realized the
whitespace-only nodes described at
http://www.w3.org/TR/1998/REC-xml-19980210#sec-element-content should be ignored.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira