Affects Version/s: 2.4.0-fuse-02-00
Fix Version/s: None
Similar Issues:Show 9 results
MR-449 Custom SOAP fault retruned to a CXF endpoint get lost when routed through JMS endpoint MR-358 trouble with camel route from cxf consumer to cxf producer MR-485 Failed to create route fromQueueToLog at: >>> Transacted[ref:null] <<< in route: Route[[From[activemq:acoss]] - ClassCastException - Camel Blueprint MR-169 ClassCastException when using camel-cxf and camel-jms in the InOut same flow MR-267 Infinite loop in running route involving CXF Endpoint MR-595 When restarting a route with inflight jms message, messages appear to be lost MR-664 When ID's are unique across the camel context and not the route. MR-652 JMS consumers not getting unregistered when camel route bundle is stopped MR-836 CxfClientCallback should not populate camel exchange OUT message if no response comes back to cxf producer and camel exchange pattern is InOnly
I need a camel route that receives a one-way JMS message, modifies the message so that its suitable for the destination web service, then invokes the external web service.
I'm thinking the following (pseudo) route could do the trick.
<bean ref="myProcessor" method="process"/>
What i'm not clear on is this the best approach? Will the myProcess step be able to transform the jms message into a payload suitable for the cxf producer endpoint? What will the process() method use - wsdl2java/jaxb object perhaps? - as the argument to setBody() on message before it goes to the cxf producer endpoint?
I can imagine an alternative approach would be for the myProcessor bean to hold on to a CXF client-side proxy (set via Spring injection) and invoke on that. That way i could just use the JAX-WS / JAXB object model to map and populate the outgoing request from the content of the JMS message.
Thoughts? Have u seen this done and/or any sample code?