I need to create a web service that can serve both rpc/encoded and
document/literal style SOAP messages, for legacy reasons. Correct me if I am
wrong, but I don't think that CXF supports rpc/encoded, so I thought that I
could write a couple of interceptors that would transform the rpc/encoded
SOAP messages into document/literal messages. The inbound interceptor seems
pretty straight forward to me. I just need to detect an rpc/encoded message
and transform it. The problem I'm having is with the outbound interceptor.
Ideally, I would like the service to be able to accept both rpc/encoded and
document/literal, but if I am translating all the rpc/encoded messages on
the way in, I won't know which messages to translate on the way out.

 

That's the setup. Now my question is, 1) Does anyone have any confidence
whatsoever that this will even work, and 2) is there some way of marking the
messages on the way in so I know which messages need to be translated on
their way out?

 

Thanks,

John

Reply via email to