Hi,
I have a similar "problem", so I would also be interested to know more
technical details. Especially about this choice/sequence thing.
I have a WSDL file with the following content:
...
...
And this is what JAX-WS/JAXB/CXF generates:
...
On Apr 16, 2014, at 7:55 AM, sfont wrote:
> Hi,
> we have solved introducing the wsdlLocation attribute in the jaws:endpoint
> configuration. We verified also that after that change if we enable the
> schema validation cxf validates the soap request and response against our
> original schema/wsd
-cxf-contains-elements-with-minOccurs-0-instead-of-a-choice-tp5742815p5742901.html
Sent from the cxf-user mailing list archive at Nabble.com.
Hi,
I'm using cxf 2.7.10 with java 6.
I have defined a wsdl with a top-down approach. In one of the xml schema
that I import in the wsdl I have defined a complex type that includes a
choice.
When I look at the wsdl that cxf generates at runtime I see that the choice
disappeared and a nillable=tru
