> 1)What use cases is the WSDLSoapServiceFactoryBean used for? (Yes I have
> looked at call hierarchy in eclipse)?
WSDLSoapServiceFactoryBean is exclusively used by CXF Soap component
(with scheme "soap") which is a component lives in camel-cxf that only
uses CXF SOAP binding not CXF transports.
> 2)Why are soap interceptors specifically registered as part of the call to
> WSDLSoapServiceFactoryBean.create()?
I am not sure. There is a comment in the initializeSoapInterceptors()
method. My guess it that it tried to skip the transport interceptors.
// do not handle any payload information here
I think typically binding and transport interceptors are contributed
by endpoint. And, it is interesting that the line
"ei.getBinding().setProperty(AbstractBindingFactory.DATABINDING_DISABLED,
Boolean.TRUE)" has been commented out.
private void updateEndpointInfors() {
Service service = getService();
for (ServiceInfo inf : service.getServiceInfos()) {
for (EndpointInfo ei : inf.getEndpoints()) {
//setup the endpoint address
ei.setAddress("local://" +
ei.getService().getName().toString() + "/" +
ei.getName().getLocalPart());
// working as the dispatch mode, the binding factory
will not add interceptor
//ei.getBinding().setProperty(AbstractBindingFactory.DATABINDING_DISABLED,
Boolean.TRUE);
}
}
}
> 3)And should I be able to use the framework of WSDLSoapServiceFactoryBean
> for handing any message type without requiring a service class and without
> having to register interceptors specfic to a particular message type?
I think it is possible.
> Regards,
> Seumas
> --
> View this message in context:
> http://www.nabble.com/Creating-a-cxf-camel-route-without-service-class-tp24293353p24293353.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
