"rferreir" wrote : Actually, the current implementation can route separated
messages for the services, since every route-to request contain a smooks trans. The idea
behind this is: You pass for the splitter a huge message (eg: An Complete Order), and the
splitter process each smooks trans for this message, and the resulting messages (Eg:
Separeted Items) are routed for the services.
I must be reading the code incorrectly in that case Ricardo. I'll have a look at your
example.
When I look at the code, it says to me, for each route-to config:
1. Apply a smooks.filterSource opp using the PayloadProcessor,
2. If there's a result, route it to the target service defined in the route-to.
So... as I read it, yes it may route multiple messages if there are multiple destinations
configured, but it routes a max of one message to each destination for a given exec of the
action. No?
"rferreir" wrote : But let's talk about improvements. I've not work yeat
with this FragmentRouter, I'm going to learn how it works and try to use in the
implementation. Could you help in this class usage?
|
| I've not found a description of this router in the programmers guide, I've
only the source code. But it seems that I should instantiate a copy of this router for
every routing that I'm planning to do, it's correct? If so, I've to pass a
instance of a executionContext that wrapps a smooks transformed object.
Take a look at the smooks_file_splitter_router quickstart in the 4.6 release.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4252885#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...