I don't know what you mean by the soap method name. the soap action header should be in the camel headers. the operation name (i.e., the operations defined in the wsdl) is not available, unless you use an endpoint that has the operation meta info (e.g., a wsdl or a generated jaxws service class) that can determine the operation based on the request message.
But going back to the beginning, I don't know what motivates you to switch to camel-http to handle soap invocations. If there is no particular reason except that you want to handle arbitrary soap messages (e.g., payload types), you can just expose a provider based service or use the default generic provider based service that can take any soap requests. When using the generic provider, you get the flexibility of taking arbitrary request messages while using some specific web service features or error handling. Its limitation is that you cannot determine the operation name as you are not using the meta data. regards, aki 2014-04-24 11:49 GMT+02:00 komal bhola <komalbh...@gmail.com>: > Hi , > > Currently I am using cxf endpoint to listen to soap requests. Actually I > want to use http endpoint only to listen to soap requests. I need to provide > different services on only 1 URL. So I want soap method name to be populated > in camel headers, based on which I can call different different services. > Please suggest a way out if any one has already tried this. > > Thanks > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Handling-soap-request-in-http-endpoint-possible-tp5750524.html > Sent from the Camel - Users mailing list archive at Nabble.com.
