Hello,
I need to propagate some custom context information (security context;
stored as header within my camel exchange) to some component that is not
directly accessible in my camel route (jaxws-handler assigned to a
cxf:client - both are singletons). Typically, I would introduce a thread
loc
aling is
processed on my camel route) Is JAXB-unmarshaling skipt with data format
PAYLOAD, even if I provide the serviceClass attribute?
Thanks,
Thomas
> On 12/14/10 5:54 AM, Thomas KRIECHBAUM wrote:
> > Hello,
> >
> > how can I assign JAXWS-handlers to an
Hello,
how can I assign JAXWS-handlers to an CXF-endpoint using data format
PAYLOAD?
The documentation
http://camel.apache.org/cxf.html#CXF-ConfiguretheCXFendpointswithSpring
suggests the child element cxf:handlers. But when starting the camel
context the following exception is thrown:
?
Cau
; On 12/09/2010 02:28 AM, Thomas KRIECHBAUM wrote:
> > Hello,
> >
> > the conversion does not help. It seams, that the second cxf-component
> > (POJO) changes the camel exchange in a way the first cxf-component
> > (PAYLOAD) can't deal with. For simplicity, I have boun
Hello,
the conversion does not help. It seams, that the second cxf-component
(POJO) changes the camel exchange in a way the first cxf-component
(PAYLOAD) can't deal with. For simplicity, I have bound both components to
the same WSDL, but even if I wrap the response from the second
cxf-componen
Hello,
in my integration prototype an existing web-service should be adapted to
an other contract. Therefore, I have a cxf:consumer(dataFormat=PAYLOAD;
the associated cxf:endpoint definition references a WSDL but no service
class) and a cxf:producer (the associated cxf:endpoint references a
se
