[ http://jira.jboss.com/jira/browse/JBESB-486?page=all ] Tom Fennelly updated JBESB-486: ------------------------------- Summary: Can ContentBasedRouter and StaticRouter "split" based on an action property, verses using a different action "process" method? (was: Can ContentBasedRouter and StaticRouter "splt" based on an action property, verses using a different action "process" method?) Description: 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!! was: These action classes both specify a pair of process method 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-486?page=all ] Kurt Stam updated JBESB-486: ---------------------------- Fix Version/s: 4.2 Milestone Release 2 (was: 4.2) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-486?page=all ] Kurt Stam closed JBESB-486. --------------------------- Resolution: Done When the message is routed to more then 1 destination we now always tag the messages. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira