I'm confused about proper use of a binding file to generate code for
nested elements. Simplified xsd:
xs:element name="a"
xs:complexType
xs:sequence
xs:element name="b" type="xs:string"/
/xs:sequence
/xs:complexType
/xs:element
What I want is a class that looks like:
class A {
The second example works, but from reading the documentation, I was
expecting the first to work also - this suggests that either my mental
model of how this is supposed to work is wrong or there is a bug in the
codegen.
Werner Guttmann wrote:
Michael,
just reading your question, I am not
Just out of curiosity, would the following binding file work for you ?
elementBinding name=complexType:a/b
member name=b
java-type=my.CompressedString
handler=my.CompressedStringHandler/
/elementBinding
Thanks
Werner
Michael Thome wrote:
The
Michael, not sure what the problem is. Maybe somebody else is capable of
providing you with a better and more helpful answer.
Werner
Michael Thome wrote:
'Fraid not. Seems to be a confusion between the implicit complexType
between a and b. I'm not quite sure what it is actually doing - I
Michael,
Try adding a forward slash (/) in front of the a/b, such as:
name=/a/b
If I recall correctly there is a bug in the binding file that requires
the extra forward slash.
Hopefully that solves the issue for you.
--Keith
Michael Thome wrote:
The second example works, but from reading
5 matches
Mail list logo