I don't have an example, but maybe the JAX-WS Provider interface could help you, much like the JAX-WS Dispatch interface[1] can handle RPC/encoded from the SOAP client side. Although, in your shoes, I would probably just stay with Axis 1.x so long as you need to maintain this service.
Glen [1] http://www.jroller.com/gmazza/entry/calling_rpc_encoded_web_services Michael Rohleder-2 wrote: > > Hi, > does anybody have a solution for providing a rpc-encoded jax-ws webservice > for backward compatibility and for giving clients time to migrate to a new > document-literal webservice? > > I think xml transformation (rpc-encoded <-> document-literal) could be > possible, like this: > http://www.cafebabe.me/2007/03/migrating-smoothly-from-rpcencoded-to.html > It detects the incoming rpc/encoded requests and transform them to the new > structure. Unfortunately this is not a generic transformation solution, > the > xsl is implemented for a specific service...perhaps anyone have a idea for > generic way? > > Are there other solutions (generators, handlers, ...)? > > Thanks. > > Michael. > -- View this message in context: http://old.nabble.com/Providing-rpc-encoded-jax-ws-webservice-tp26702740p26705182.html Sent from the cxf-user mailing list archive at Nabble.com.
