On thinking this over, I realized it's more complex than we'd discussed.
You're assuming that the choice has minOccurs='1', but it's equally
valid for a choice to have minOccurs='0' (or maxOccurs 1, but that
equates to a collection). I suppose what I should really do is see if
the binding
Hi Steven,
I don't see anything obviously wrong with what you're doing. Here's a
sample from the JiBX build test cases:
mapping name=myelement class=simple.MyClass3
structure ordered=false choice=true
value name=a field=a usage=optional/
value name=b field=b usage=optional/
Dennis Sosnoski [EMAIL PROTECTED] writes:
Here's a sample from the JiBX build test cases:
mapping name=myelement class=simple.MyClass3
structure ordered=false choice=true
value name=a field=a usage=optional/
value name=b field=b usage=optional/
value name=c field=c
Steven E. Harris wrote:
Dennis Sosnoski [EMAIL PROTECTED] writes:
Here's a sample from the JiBX build test cases:
mapping name=myelement class=simple.MyClass3
structure ordered=false choice=true
value name=a field=a usage=optional/
value name=b field=b usage=optional/
I'm struggling trying to figure out the right way to write a binding
for an xsd:choice structure. Consider the following schema fragment:
xs:simpleType name=Tmac-48
xs:restriction base=xs:string
xs:pattern value=[\p{Nd}A-F]{2}(-[\p{Nd}A-F]{2}){5}/
/xs:restriction
