This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.
There are no samples that I know off, but I can't imagine it to be hard at all. All you need is to simply inject the reference to a Messaging Gateway (e.g., <gateway>) to your CXF component and you got the integration you are looking for.
I am experimenting with this right now. We are trying to leave our business services free of cxf annotations, which means creating a separate SEI/implementation that would in turn call the business services. Without SI that involves the implementation method calling the relevant business service method directly. To link this with SI, unfortunately it looks like it might require editing each method in the SEI's implementation to manually put a message on a channel. This would in turn probably invoke a service-activator for the business service with a reply channel. Then the SEI implementation method would receive the message from the reply channel to return it, for CXF to handle.
This seems ugly and it would be preferable to be able to edit the jaxws configuration to call an SI gateway directly. But the part I'm stuck on is that it seems that is a one-way trip and I'm not sure how to make it automatically return the response that the business service would eventually return.
By doing that I was able to remove our implementation for our SEI. The part that is non-obvious in the implementation is that the business service method's response gets passed back on a temporary channel to the SEI's implementation (the gateway), which is then returned for CXF to handle.
Last edited by tunesmith; Oct 3rd, 2012, 06:51 PM.