You can invoke the web service using plain HTTP
But for that you must make sure the payload is SOAP. And you may have to set the SOAPAction header etc.
For CXF you can use the MESSAGE or PAYLOAD data format mode. Then you do not need to generate source code using wsdl2java
See this page for descriptions on the data format mode and what they mean.
If you look at this CXF proxy example
Then notice how it uses the MESSAGE data format mode. You should be able to do something similar for the
SoapUI is a good tool to test web services and see how a working request look like.
I was succesful using the http approach when I set the header Content-Type to xml.
Is there any advantage using cxf ?
If you can prepare the request message and consumer the response message yourself, camel-http component could be your first choice.
If you want to some other WS* work and turn the message into some data format, you may think about using camel-cxf component.
If you simply wanna a proxy, http might be enough,
But if cxf component absolutely is more powerful and flexible if you want to get involed more about handle soap message.
Thanks a lot.
For the first time the http approach works fine but I think I will try the same with the cxf components......