Hi Wilson,
I am afraid you need to provide the SEI class for camel-cxf component
to initiate the endpoint.
If you do not want to unmarshal the request message , I think you could
use soap message or raw message data formate.
Now I am thinking to do some refactoring work to enable the web
services endpoint without SEI class.
Willem.
Wilson wrote:
Hi Willem,
Is the serviceClass URI parameter mandatory? Do I need to provide a Java
Class to use CXF routing? It is not possible to use WSDL first like in
Servicemix CXF-BC component?
Thank you,
Wilson
willem.jiang wrote:
Hi Wilson
CAMEL-180 is just using CXF SOAP interceptors to handle the SOAP
message.
In you case , you would use camel cxf component to router a soap request
to another external web service.
Here is an example[1] in camel of routing a SOAP over HTTP request to a
SOAP over JMS web service.
[1]
https://svn.apache.org/repos/asf/activemq/camel/trunk/examples/camel-example-cxf
Willem.
Wilson Freitas wrote:
Hi,
I've found the new feature described in
https://issues.apache.org/activemq/browse/CAMEL-180
In the issue description, there is this item:
*Supporting to create server and client without SEI
I've downloaded the newer 1.3-snapshot. I tryied to unsdesrtand how to do
this in the component unit testes, but i was unable to figure out how to
create server/clients.
What I want to do is:
External client----SOAP---->(Camel routing)-----SOAP------>External Web
Service
I want to use Camel as a webservices hub.
It is possible to do that?
Thank you,
Wilson
