WS-I BP 1.0 and 1.1 both say that a web service must support any valid
XML Schema construct, but it doesn't require that the SOAP engine
automatically map the construct to an object for you. JWSDP is WS-I
compliant. It supports <xsd:choice> by mapping it to SOAPElement.
On 5/8/05, Alessio Cervellin <alessio.cervellin_at_sun-cs-italy.com> wrote:
> Kevin Jones wrote:
>
> > When you say it doesn't support xsd:choice what exactly do you mean?
>
> I mean that when running wscompile it exactly says "unsupported XML
> schema feature: 'xsd:xhoice' in componenent ..."
> I know it maps it to a SOAPElement, but I was expecting instead a
> mapping to an object (like jax-rpc 2.0 seems should do), so I was
> wondering why xsd:choice was not supported by jax-rpc 1.x: is it
> something due to some specifications? At least in the WS-I BP1.0
> specifications the element xsd:xhoice is being used.
>
> ---------------------------------------------------------------------
> 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
>
>