L.S., If you use Java code inside a CXF-SE endpoint to translate and send off the exchange to the provider endpoint, you will have to deal with the JBI message API yourself, while using Camel, you will only have to do the translation bits and have servicemix-camel handle the JBI messaging mechanics. Personally, I would prefer using Camel for this, but either way should work fine for you.
Regards, Gert Vanthienen ------------------------ FuseSource Web: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ On Mon, Jan 2, 2012 at 4:56 PM, Rafal Janik <[email protected]>wrote: > Hi > > I want to implement something like that : > 1 cxfbc consumer consumes a soap > 2 soap is mapped to the java object > 3 I get some information from that object - we can say I want to translate > it into another object > 4 via cxf bc provider it is sent to external web-service > 5 response is translated and sand back to the client > > In SMX 4 it is quite easy, here I have a problem how to do that in right > way... > So OK - as I understand there should be of course cxfbc consumer and > provider. > But where should be translation done ? > First idea is to implement a a cxf se unit and inside it map the object to > another type, then packed it with JAXB and send via NMR to provider > endpoint. > Is it good solution? > Or maybe I can or should use Camel here? But if yes - there is no need to > use cxf se as I understand - isn't it? Just a bean which will deserialize > xml to java object, translate it and serialize again? > > > regards > > > rafal > >
