That's right -- JWSDP is JAX-RPC compliant. It won't map a <choice>
compositer to an object for you, but it will map it to SOAPElement.
On 5/8/05, Kevin Jones <kevinj_at_develop.com> wrote:
> When you say it doesn't support xsd:choice what exactly do you mean? If I
> use xsd:choice in JWSDP then I get generated code that uses SOAPElement. I
> can then use SAAJ to produce/extract the data,
>
> -----Original Message-----
> From: Alessio Cervellin [mailto:alessio.cervellin_at_sun-cs-italy.com]
> Sent: 06 May 2005 18:04
> To: users_at_jax-rpc.dev.java.net
> Cc: belen.montero_at_sun.com; roberto.cardoni_at_sun.com
> Subject: xsd:choice support
>
> Hi all.
> As far as I can see it seems that wscompile (of JWSDP 1.5) doesn't support
> the <xsd:choice> element.
> My questions are:
> 1) is there a reason for that? According to the WS-I BP1.0 specifications it
> should be supported (AFAIK)
> 2) is there any equivalent syntax to replace in a WSDL which uses the above
> element?
> 3) if not, are there any other workaround to use it?
>
> Note: Axis does support it... :P
>
> Thanks.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
> For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
> For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
>
>