camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ssoltysik <seumas.solty...@progress.com>
Subject Creating a cxf-camel route without service class
Date Wed, 01 Jul 2009 16:55:34 GMT

I would like to be able to create a route using payload mode using camel-cxf
without having to specify a service class. The current
ReflectionServiceFactoryBean which is used by ServerFactoryBean requires
that a service class be specified. I see however, that there is  a
WSDLSoapServiceFactoryBean which seems to be along the lines of what I am
trying to do. However, I don't really understand how it is being used.
Specifically, I don't understand why it is soap specific and why it
specifies all the soap specific interceptors as part of creating a Service.
I would expect that all the required soap interceptors would be
auto-magically registered when the binding was initialized as is done
normally as part of creating the binding. Furthermore I a don't understand
why an InvokerInterceptor is not registered as part of the creation of the
Service. Even if there is no service class there still should be an invoker
to forward message to camel infrastructure.
So my basic questions are:
1)What use cases is the WSDLSoapServiceFactoryBean used for? (Yes I have
looked at call hierarchy in eclipse)?
2)Why are soap interceptors specifically registered as part of the call to
WSDLSoapServiceFactoryBean.create()?
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?
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.


Mime
View raw message