1 of 1 people found this helpful
ExchangeInterceptor would be an option, but note that it is invoked for every exchange - if you have SOAP-in--->Bean--->SOAP-out, then ExchangeInterceptor would be invoked twice. Another option would be a custom MessageComposer on the SOAP inbound binding.
I almost forgot to mention about yet another option, you would be able to have a plain JAXWS endpoint in a war with SwitchYard service reference injected. No quickstart demonstrates exactly same scenario yet, but multiApp demo would be helpful to see how SwitchYard service reference is injected into JavaEE component. It's a JSF managed bean in this demo.
Thank you very much for the reply.
That's right, if i use the ExchangeInterceptor i have to detect if the current exchange is for "SOAP in" or any other.
The MessageComposer seems to be the better alternative to me, because no special detection is needed.
The plain JAXWS endpoint is another interesting option, but i don't want to implement the JAXWS endpoint by myself.
Because generally SwitchYard does this very well.