JAX-RPC 2.0 enhancements and changes - feedback requested

From: Doug Kohlert <Doug.Kohlert_at_Sun.COM>
Date: Wed, 14 Jul 2004 15:06:37 -0700

With the implementation of JAX-RPC 2.0 underway, now is the perfect time
for you to let the JAX-RPC SI team
know what enhancements you would like added to the 2.0 implementation.
We of course cannot promise anything
but we would like to incorporate your suggestions if possible given
time-constraints, etc.

For current users of wscompile/wsdeploy, we would like your feedback on
some potential changes that the SI
team might make in 2.0.

When JAX-RPC 1.0 was specified, it was believed that web services would
focus on rpc/encoded. However,
since that time, the industry has shifted and it appears that
document/literal is the preferred mode. Currently,
both wscompile and wsdeploy default to rpc/encoded. The question is:

Should wscompile and wsdeploy leave the default mode as rpc/encoded for
backwards compatibility reasons, or
should the default be changed to document/literal? If the default is
changed, we need to provide a way to get
the old behavior so I pose a second question. Should we add new
commands such as wscompile1 and wsdeploy1 that
have the old behavior, or should we simple add a -f:rpcencoded flag to
the existing commands? If anyone has other suggestions
we would entertain them as well.

Thank you

Doug Kohlert
Sun Microsystems, Inc.   
To unsubscribe, e-mail:
For additional commands, e-mail: