"rferreir" wrote : I've just not understood the third suggestion. When you
say that in the "route-to" tag the user could just put a XML fragment, you meant
use XPath? Or, the XML fragment that are written in the configuration IS the message that
are to be sent for the message channel?
Right... so the fragments specified by the path can be filtered and serialized to XML,
which are then routed to the specified service. Maybe it would be better to leave this
for now and concentrate on the existing features and getting them right first. What do
you think?
It also just dawned on me Ricardo... looks like you're routing to the target service
after filtering the complete message through Smooks. If so.... won't this then just
work for a single fragment? What if you want to seperately split and route each
order-item in an order i.e. so you need to be able to route multiple instances of the same
fragment from a single message? Maybe it would be better to use the existing
FragmentRouter class from the ESB, which basically wraps the ServiceInvoker inside a
Smooks Visitor, allowing you to route fragments as part of the filtering process Vs doing
it in batch at the end. What do you think?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252762#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...