users@jax-ws.java.net

Re: Encoded use

From: Vivek Pandey <Vivek.Pandey_at_Sun.COM>
Date: Tue, 10 Apr 2007 17:58:25 -0700

Right. As agreed by submitter I have updated this issue to only reflect
rpc/encoded wsdl support.

thanks,

-vivek.

Peter Hendry wrote:
> This issue was updated to include "document/encoding". However, there
> isn't really such a thing (and, considering this, I'd be surprised to
> find toolkits supporting it)!
>
> Consider that rpc provides a wrapper element (the method element) into
> which parameters can be marshalled with a child element for each
> parameter (optionally omitted). The parameter element names are taken
> from the part names. Now, consider for document. Where would the
> wrapper (method) element come from? There is no equivalent rule for
> document because the body element for document style comes from the
> schema element referenced from the message part. In the sample WSDL
> given in the issue the message part uses "type" instead of "element".
>
> The idea of Document style is that a single "document" is sent as the
> body payload. This document is specified by a schema of some sort
> (currently XML Schema) and can be validated against that schema. RPC
> is there to allow language level (as opposed to document level)
> semantics and so things like multirefs are supported (which break
> validation).
>
> The issue should be updated to remove the document/encoding reference
> so people can vote for rpc/encoded and not encumber the person
> assigned the issue with implementing some odd-ball support for
> document/encoded just because it was in the issue. If someone believes
> that there is some reason to implement document/encoding then it can
> go into a separate issue and get voted on separately.
>
> Pete
>
> Vivek Pandey wrote:
>> Dima Gutzeit wrote:
>>> Sorry, document/encoded has no sense and rpc/encoded is not supported.
>>>
>>> Is encoded style supported at all at jaxws ? What are the plans for
>>> it ?
>>>
>> See Issue: https://jax-ws.dev.java.net/issues/show_bug.cgi?id=135. We
>> may support rpc/enc in some future release.
>>
>> -vivek.
>>> Regards,
>>> Dima Gutzeit.
>>>
>>> Dima Gutzeit wrote:
>>>> Hi,
>>>>
>>>> I am defining webservices using :
>>>>
>>>> @SOAPBinding(style = SOAPBinding.Style.DOCUMENT, use =
>>>> SOAPBinding.Use.ENCODED)
>>>>
>>>> but the WSDL produced uses RPC with literal.
>>>>
>>>> What am I missing here ?
>>>>
>>>> The annotation defined on both interface and service implementations.
>>>>
>>>> Regards,
>>>> Dima Gutzeit.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe_at_jax-ws.dev.java.net
>>>> For additional commands, e-mail: users-help_at_jax-ws.dev.java.net
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_jax-ws.dev.java.net
>>> For additional commands, e-mail: users-help_at_jax-ws.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_jax-ws.dev.java.net
>> For additional commands, e-mail: users-help_at_jax-ws.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jax-ws.dev.java.net
> For additional commands, e-mail: users-help_at_jax-ws.dev.java.net
>