]
Kurt Stam updated JBESB-486:
----------------------------
Fix Version/s: 4.2 Milestone Release 2
(was: 4.2)
Can ContentBasedRouter and StaticRouter "split" based on an
action property, verses using a different action "process" method?
------------------------------------------------------------------------------------------------------------------------------
Key: JBESB-486
URL:
http://jira.jboss.com/jira/browse/JBESB-486
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Content Based Routing
Affects Versions: 4.0
Reporter: Tom Fennelly
Assigned To: Kurt Stam
Priority: Minor
Fix For: 4.2 Milestone Release 2
These action classes both specify a pair of process methods called "process"
and "split". If process is called, the MessageRouter class WILL NOT be
requested to add the aggregatorTag info. If "split" is called, the
MessageRouter class WILL be requested to add the aggregatorTag info.
Would it not be more appropriate to do this via an action property (split=true or
split=false).
In fact, the naming of this seems a little odd to me. In effect, the split is happening
either way, yes/no?? It's simply a case of whether or not the aggregation info is
added to the message or not. yes/no?
What would be the downside to always adding the aggregation info and not bothering with
this flag - if it gets used further on in the flow, great... if it doesn't, it's
no big deal!!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: