It is quite easy you need just to add the recipient list into the
xbean.xml and you are good to go (the EIP explains quite nicely. The
only thing I don't like about this approach is that the routing is
done through message exchanges.
I would rather like to have a service that delivers the next recipient
back to the mediator and the mediator would then call the service by
itself. This way the meditator has full control over how the messages
are routed to the targets like the exchange pattern, synchronous or
asynchronous exchange, response handling and much more.
Is something like that already possible? Or would other be interested
in something like that?
Thanks
Andreas Schaefer
CEO of Madplanet.com Inc.
[EMAIL PROTECTED]
On Nov 6, 2007, at 11:10 AM, willygold wrote:
Hello,
Thank's for your very nice answer. It seems that as soon as we need to
process a chain of components we need either :
- a BPEL Orchestrator
- or a java dedicated component
The Static routing slip is exactly what I need : a simplified
orchestrator
(without BPEL)
I just have to find now the documentation of this component ;)
Willy
Gert Vanthienen wrote:
L.S.,
You can use a static routing slip and add the 'return chain' XSL-T
after
the call to the external webservice:
HTTP Consumer -> Static routing slip (XSL-T -> HTTP Provider -> XSL-
T)
Gert
willygold wrote:
Hi,
I have the following chain :
HTTP Consumer -> XSLT SE -> BC Provider -> external webservice
How do the BC response message returns to the HTTP Consumer?
How is it possible to catch the BC response via another XSLT SE in
order
to
transform the response before sending it to the HTTP Consumer?
For example for the return chain :
external webservice -> BC Provider -> XLST SE -> HTTP Consumer
Thank's
--
View this message in context:
http://www.nabble.com/How-can-I-process-a-BC-response-message-tf4736948s12049.html#a13613684
Sent from the ServiceMix - User mailing list archive at Nabble.com.
