OR help implement choice in ADB :) i highly recommend that because i've seen some perf issues with xmlbeans (check xmlbeans jira)
-- dims On 1/24/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: > Hi Chuck, > The choice element is not handled in the ADB schema compiler yet (at least > we are not sure what is the best way to deal with it). Right now we do not > throw any exceptions but silently skip that (that is why the empty class) > Please use XMLBeans if you need the support for choice for now. > > > On 1/24/06, Chuck Williams <[EMAIL PROTECTED]> wrote: > > I have a complexType that contains a <choice> of two alternative > > elements, like this: > > > > <xsd:complexType name="AorB"> > > <xsd:choice> > > <xsd:element name="A" type="xsd:string"/> > > <xsd:element name="B" type="xsd:string"/> > > </xsd:choice> > > </xsd:complexType> > > > > and a reponse message that contains a value of this type: > > > > <message name="respmessage"> > > <part name="resp" type="asxsd:AorB"/> > > </message> > > > > and a portType with an operation that returns the response message: > > > > <portType name="FooPortType"> > > <operation name="Bar"> > > <input .../> > > <output message="as:respmessage"/> > > </operation> > > </portType> > > > > WSDL2Java generates a class AorB and requires it as content of the > > respmessage to be returned from the Bar() method in the generated > > FooPortTypeSkeleton. However, AorB has no setters or getters, so there > > is no way to give it the A or B element to return. Also, A and B do not > > extend AorB so there is no way to pass either of them directly. > > > > How is this supposed to work? > > > > Thanks for any help, > > > > Chuck > > > > > > > > -- > Ajith Ranabahu -- Davanum Srinivas : http://wso2.com/blogs/
