You can use Camel too to implement EIP. Most of the time, the DSL is
simpler.
Regards
JB
iocanel wrote:
gnanda wrote:
Could I use bean class to call http endpoint without using servicemix
client ??
Yes, using the delivery channel, combined with an eip endpoint
(pipeline,routingslip are most suitable) that will help you send the OUT of
the Exchange to the proper endpoint.
gnanda wrote:
If I make my bean to handle inOut exchange and call
channel.send(outexchange), would that call http end point ?
The pipeline or the routingslip. Here are simplified examples:
<-! Using the Pipeline -->
<!-- Jms Consumer Sends InOnly to Pipeline. Pipeline sends a copy of InOnly
as InOut to bean. Bean produces sets Out Message on the Exchange and sends
to Delivery Channel. Pipeline sends the Out as InOnly to http provider -->
<eip:pipeline service="sns:pipeline" endpoint="eipEndpoint">
<eip:transformer>
<eip:exchange-target service="sns:bean" />
</eip:transformer>
<eip:target>
<eip:exchange-target service="sns:http-provider" />
</eip:target>
</eip:pipeline>
Finally you mentioned that you want to decide dynamically where to send the
message. This can be done with various ways from using camel recipient lists
to implementing some custom logic inside the http provider marshaler. You
are free to choose.
Now, if the transaction issue you had, has been solved, it might be a good
idea to start a new thread about the bean endpoint and the dynamic routing,
to keep this clean.
-----
Ioannis Canellos
