Thanks for the info... I am able to do that now with the help of
<camel:convertBodyTo type="java.lang.String" /> tag along the route to
convert the SOAPMessage to string...
I have an other doubt; While configuring Camel CxF endpoints through spring
configuration like below,
<cxf:cxfEndpoint id="serviceEndPoint"
address="http://localhost:8080/websvc/JaxWsService";
serviceClass="com.websvc.jaxws.JaxWs"/>
Are there any way of configuring URL host/port dynamically in Spring
configuration ?
any link to tutorial to test case would help..
Thanks.
willem.jiang wrote:
>
> Hi,
>
> It dependents on what kind of message that you can get from the servlet.
>
> If you can got the SOAP request message from the servlet (The message
> body can be an InputStream), you can just redirect the message or do
> some transforming work on the message then send the message to the
> camel-http[1] endpiont.
> Then you can get the SOAP response from the camelTemplate.
>
> Otherwise, you can build the SOAP request message which is based on the
> servlet request youself, then pass it to camel-http[1] endpoint.
>
> Or you can take a look at camel-cxf's PAYLOAD dataformat[2], which also
> can help you to send and receive the SOAP message with header.
>
> [1]http://camel.apache.org/http.html
> [2]http://camel.apache.org/cxf.html#CXF-HowtogetandsetSOAPheadersinPAYLOADmode
>
> Willem
>
> Winsks wrote:
>> My route is like this,
>>
>> <camel:camelContext id="CamelContext"
>> xmlns="http://activemq.apache.org/camel/schema/spring";
>> shouldStartContext="true">
>> <camel:template id="camelTemplate"/>
>> <camel:route>
>> <camel:from uri="direct:start" />
>> <camel:process ref="InService" />-->
>> <camel:to
>> uri="cxf://http://localhost:8080/websvc/JaxWsService?serviceClass=com.websvc.jaxws.JaxWs";
>> pattern="InOut"/>
>> <camel:process ref="OutService" />
>> </camel:route>
>> </camel:camelContext>
>>
>> If I do the template.sendbody(direct:start, ? ) , say from a servlet,
>> what
>> type the body should be ?
>> Also how to get back the SOAPMessage response from it with the headers ?
>>
>> Thanks
>>
>>
>> willem.jiang wrote:
>>> Hi,
>>>
>>> What's your usecase ?
>>>
>>> If you just want to use camel to invoke the service, you can try
>>> camel-http component.
>>> If you want to implement a proxy service , you can use camel-jetty.
>>>
>>> BTW, CXF implement the JAXWS spec, so the artifacts of the glassfish
>>> metro can smoothly port to CXF.
>>>
>>> Willem
>>>
>>> Winsks wrote:
>>>> firstly, thanks for the gr8 job u guys are doing!!!
>>>>
>>>> I m new to camel and I m interested in using Camel as a
>>>> routing/mediation
>>>> engine for a set of webservices developed and hosted in glassfish
>>>> metro.
>>>> What is the best approach in developing this route engine: camel cxf /
>>>> camel
>>>> http / camel jetty component for the endpoints ? i am not able to find
>>>> any
>>>> examples without using CXF. Any help /advice is greatly appreciated.
>>>>
>>>> thanks
>>>
>>>
>>
>
>
>
--
View this message in context:
http://www.nabble.com/newbie%3A-Camel-for-Non-CXF-webservices-tp25402219p25493990.html
Sent from the Camel - Users mailing list archive at Nabble.com.
