Hi,
Both way should work here.
If you chose to use cxf se, you can use cxfse:proxy as the client to
invoke the cxfbc:provider, this way you needn't use jaxb to do marshal
yourself, the cxfse:proxy works as a normal object invocation, the
work flow is
cxfbc:consumer===>cxfse===>cxfse:proxy====>cxfbc:provider
Take a look at [1] to get more details about how cxfse:proxy works,
the "Proxies" part.
[1]http://servicemix.apache.org/servicemix-cxf-se.html
Freeman
On 2012-1-2, at 下午11:56, Rafal Janik 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
---------------------------------------------
Freeman Fang
FuseSource
Email:[email protected]
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
