Sameer Pradhan
2005-06-29 21:41:33 UTC
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
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