I think you have to provide a serviceClass in this case. The serviceClass is only retrospected to create a CXF service endpoint. Yes, If you specific PAYLOAD mode, the XML message unmarshalling to Java will not be performed by the Camel-cxf endpoint.

It's looks you are using the simple front end which means there is no
@WebService annotation in your SEI.
Current we don't support the JAXWS-handler in simple front end, please
make sure you are using the jaxws front end.
Does this mean that I have to provided the serviceClass attribute at the
cxf:cxfEndpoint? Since the incoming SOAP-Message is not wellformed in some
cases (e.g. timestamp format), the SOAP message should not be mapped to
the JAXB classes directly (this is the reason, why I'm using data format
PAYLOAD; I'm doing some message correction before JAXB unmarshaling is
processed on my camel route) Is JAXB-unmarshaling skipt with data format
PAYLOAD, even if I provide the serviceClass attribute?

Thanks,
Thomas


Reply via email to