Anne,
You can also use the r2d tool provided by Microsoft under their GOT DOT NET community website,
to generate the wire format described with a WSDL which use RPC-literal message format.
I assume - also I have not tried it - this tool could also be used to generate the XML Schema
if once wanted to validate the entire SOAP body within an intermediary node which is
not a SOAP node.
eric
Anne Thomas Manes wrote:
> Perhaps it is. But regardless of the impetus behind the behavior, the
> fact remains that .NET doesn't support RPC/Literal. If you want to build
> a service that interoperates with .NET, you should use Document/Literal.
>
> At 06:56 PM 3/24/2004, you wrote:
>
>> Anne Thomas Manes wrote:
>>
>>> There are lots of people at WS-I that really wanted to exclude the
>>> RPC convention from the BP. But WS-I works by consensus, and it was a
>>> very divisive issue.
>>
>>
>> For the record, W3C works by consensus, WS-I does not. Working in a
>> standards body, losing a vote on one issue, then proclaiming that
>> you support the resulting standard all while refusing to support
>> the one feature on which you got outvoted is, well, "childish".
>>
>> Roberto
>>
>> --
>> Roberto Chinnici
>> Java Web Services
>> Sun Microsystems, Inc.
>> roberto.chinnici_at_sun.com
>>
>> ---------------------------------------------------------------------
>> 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
>
>
> ~~~~~~~~~~~~~~~~~~
> Anne Thomas Manes
> VP & Research Director
> Burton Group
>
> ---------------------------------------------------------------------
> 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