Details
Bug
Closed
Minor
Description
Castor XML does not unmarshall the following XML document:
<?xml version="1.0" encoding="UTF-8"?>
<xcap-directory xmlns="urn:oma:xml:xdm:xcap-directory" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<folder auid="resource-lists"/>
</xcap-directory>
With the classes generated from the XML schema for XDM - XCAP Directory (http://www.openmobilealliance.org/tech/profiles/xdm_xcapDirectory-V1_0_1.xsd).
We found a workaround specifying minOccurs="0" in the <xs:choice> element definition of the schema.
Original schema from Open Mobile Alliance is attached to this bug report.
The modified schema to make castor to work is also attached.
Attachments
Activity
If I understand correctly you would rewrite the schema in such a way (moving cardinality to elements) ?
<xs:choice>
<xs:sequence>
<xs:element name="entry" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
[...]
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:element name="error-code" type="xs:string"/>
</xs:choice>
I will try that on monday in my dev environment to see if Castor is happy with that 
The server returns a folder that can contain 0 to n entries (like files) OR an error code OR nothing (e. <folder auid="resource-lists"/>)
The server returns a folder that can contain 0 to n entries (like files) OR an error code OR nothing (e. <folder auid="resource-lists"/>)
Does the following fragment of the original schema make sense at all:
<xs:sequence minOccurs="0" maxOccurs="unbounded">
Normally one uses a sequence to define a sequence of elements for a complex type, and specifies the cardinality of the individual elemenst at the element level. Hmm .. just thinking aloud.