|
Having just gone through a similar exercise: 1. I think the correct approach ought to be to attach the min/max attributes to the choice rather than to the sequence - e.g. you want a single sequence of any number of a choice of {and,or,not} elements, not any number of sequences of a single choice. 2. but: although both can be used perfectly fine with the expected documents and validation, wsdl2java appears to silently ignore min/max attributes on non-element declarations. 3. A search of Jira shows several relevant outstanding bugs: http://issues.apache.org/jira/browse/AXIS-236 http://issues.apache.org/jira/browse/AXIS-600 Until fixed, I think the only way to work around the problem is by putting the min/maxOccurs on the elements, e.g:
cheers,mik Bill Keese wrote:
|
- Re: xsd:choice (and WSDL2Java) Michael Thome
- Re: xsd:choice (and WSDL2Java) Bill Keese
- Re: xsd:choice (and WSDL2Java) Michael Thome
- Re: xsd:choice (and WSDL2Java) Michael Thome
- Re: xsd:choice (and WSDL2Java) Michael Thome
- Re: xsd:choice (and WSDL2Java) Bill Keese
