Hi Christopher,
You are right in your approach. By importing your CXF web service into
Camel, you will benefit of the camel power to extract the payload of the
message and send it to a queue/topic where different subscribers are
listening
here is an example that you can follow :
<cxf:cxfEndpoint id="service"
address="http://localhost:9000/service"
serviceClass="com.mycompany.service.impl.ServiceImpl"
dataformat="PAYLOAD"
/>
<camelContext id="camel" trace="true"
xmlns="http://activemq.apache.org/camel/schema/spring">
<route>
<from uri="cxf:bean:service" />
<to uri="bean:tracker" />
<to uri="jms:queueTopic" /
</route>
</camelContext>
<bean id="tracker" class="com.xpectis.tracker.bean.ExtractPayaload"/>
Remark : It is perhaps possible to extract directly the Payload without
sending the message to a Bean using the option dataformat=PAYLOAD but
personally I haven't test it
KR,
Christopher
huntc wrote:
>
> Hi there,
>
> I'm looking for a little guidance on best-practice use of CXF and Camel.
>
> I have a CXF based web service and I would like to publish the payload it
> receives to a topic. I then want various subscribers to the topic to
> receive the payload and subsequently process it.
>
> My CXF service is presently housed in a Tomcat container, but I'm thinking
> that I should use the Spring container and house a Camel context. I would
> then declare my CXF service to my Camel context so that I could route from
> it.
>
> Does this sound like the right approach?
>
> If so then does my CXF service implementation become obsolete? i.e. is it
> just my SEI that gets used if all that I want to do is publish the payload
> it receives to the topic?
>
> Kind regards,
> Christopher
>
-----
Enterprise Architect
Xpectis
12, route d'Esch
L-1470 Luxembourg
Phone +352 25 10 70 470
Mobile +352 621 45 36 22
e-mail : [EMAIL PROTECTED]
web site : www.xpectis.com www.xpectis.com
My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/
--
View this message in context:
http://www.nabble.com/Camel-inside-CXF-or-CXF-inside-Camel-tp20030207s22882p20030416.html
Sent from the Camel - Users mailing list archive at Nabble.com.