Switch to "WRAPPED" style. It produces document/literal services, and yet it supports the same programming model as rpc/encoded. You will need to convert your soap encoding arrays to literal arrays, but that should happen automatically for you if you simply regen your wsdl using java2wsdl. Some tweaking may be required. The same tweaking would also be required if you switched to RPC/literal, but WRAPPED gives you must better interop with other environments -- especially .NET (which doesn't support rpc/literal).
Anne On 6/29/05, Sameer Pradhan <[EMAIL PROTECTED]> wrote: > > > > Hi everyone, > > > > I have some webservices implemented in java and deployed in AXIS. These are > deployed as RPC/encoded services. We have a new requirement to make all > webservices WS-I compliant. The ones I referred above are not WS-I compliant > because RPC/encoded is not allowed in WS-I Basic Profile. > > > > I need help to evaluate my options: > > > > 1. Switch to RPC/literal services. Is this advisable? The services use > soap-encoded arrays of objects and xsd:strings. Can these be supported in > rpc/literal services? Where can I find documentation/instructions on how to > set up rpc/literal services in AXIS? > > > > 2. Switch to document style services. Is this a better option? If so, why? > Would I need to rewrite the implementation? Again, where can I find > documentation/instructions on how to set up document style services in AXIS? > > > > Any other options? > > > > Any help will be appreciated. > > > > Sameer > >
