Hi Christian, Thanks for your response. Camel Http component worked but that is not what we are looking for. Following are the reasons:
1. The routes are usually created by the clients and they range from simple to complex. Along with the routes they provide XSLT mappings which will essentially only work on payloads. For using HTTP component i had to change the XSLT to add a soap envelop so that when a HTTP call is made to the external webservice it does not fail because after application of XSLT on the payload there is no soap envelop. 2. If we use ServiceMix along with CXF we can easily do this by creating cxf consumers and producers so i am not sure why is this so difficult to do using cxf and camel. I am planning to debug the Camel CXF codebase to see why OperationBindingInfo is not found even when we explicitly set it on the producer. Thanks & Regards, Madhav Schneider Christian wrote: > > Status code 500 means internal server error. I guess the endpoint you sent > the request to was not able to process the request. Perhaps you will have > more details in the log of this endpoint. > > It could be some invalid soap for that service... > > Best regards > > Christian > > Christian Schneider > Informationsverarbeitung > Business Solutions > Handel und Dispatching > > Tel : +49-(0)721-63-15482 > > EnBW Systeme Infrastruktur Support GmbH > Sitz der Gesellschaft: Karlsruhe > Handelsregister: Amtsgericht Mannheim HRB 108550 > Vorsitzender des Aufsichtsrats: Dr. Bernhard Beck > Geschäftsführer: Jochen Adenau, Hans-Günther Meier > > -- View this message in context: http://camel.465427.n5.nabble.com/Calling-external-webservice-using-cxf-camel-endpoint-tp3238383p3238726.html Sent from the Camel - Users mailing list archive at Nabble.com.
