So it appears that you are want to add support for having choice and group
elements within the sequence.
In addition it appears that the group element must be a definition of the
group (rather than a ref to an existing group).
In all of these cases the code is merely diving deeper to find nested
elements.
Seems like a reasonable first pass. I will add the code and see if it
breaks any tests
I am going to change processElementNode to processChildElementNode...
Thanks,
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
R J Scheuerle
Jr/Austin/IBM@IBM To: [EMAIL PROTECTED]
US cc: "'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>
Subject: RE: [PATCH] Support for
xsd:choice
02/15/2002 04:21
PM
Please respond to
axis-dev
I'll look at it right now and comment shortly.
Thanks
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
David Altenburg
<altenburgd@busines To:
"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
slogic.com> cc:
Subject: RE: [PATCH]
Support for xsd:choice
02/15/2002 02:33 PM
Please respond to
axis-dev
I'm curious as to why this patch has not been commented upon. The
functionality it provides is not only useful to my organization, but it
takes AXIS a step (albeit small) closer to supporting all of XML Schema.
If there is a specific reason as to why this cannot be committed, or if
there is anything else I need to do before it can be considered for
committal, please let me know.
Thanks,
David Altenburg
-----Original Message-----
From: David Altenburg
Sent: Tuesday, February 12, 2002 3:37 PM
To: [EMAIL PROTECTED]
Subject: [PATCH] Support for xsd:choice
Attached is a patch that adds some support for xsd:choice elements.
Currently, that just means creating getters and setters for everything that
may be present. It does not do the ChoiceCompositor stuff that James
Yegerlehner proposed, but it does create a base onto which that could be
added.
David Altenburg
[EMAIL PROTECTED]
