esb-issues April 2007

esb-issues@lists.jboss.org

1 participants
164 discussions

[JBoss JIRA] Created: (JBESB-497) JMSEpr helper class doesn't seem to be generating the endpoint URI properly

by Tom Fennelly (JIRA)

JMSEpr helper class doesn't seem to be generating the endpoint URI properly --------------------------------------------------------------------------- Key: JBESB-497 URL: http://jira.jboss.com/jira/browse/JBESB-497 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2 Milestone Release 1 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 4.2 Milestone Release 2 If you call JMSEpr.getAddr.getAddress() it always returns simple "jms://queue" - no host or destination info in the URI. -- 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

17 years

2
9
0 / 0

[JBoss JIRA] Commented: (JBESB-418) Catch-All/Otherwise/Default for CBR

by Kurt Stam (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-418?page=comments#action_12359169 ] Kurt Stam commented on JBESB-418: --------------------------------- Added a "Filter class". For a filter it's ok to have "No destination". For a router it is not. Still need to add it routing the message to a DLQ service. > Catch-All/Otherwise/Default for CBR > ----------------------------------- > > Key: JBESB-418 > URL: http://jira.jboss.com/jira/browse/JBESB-418 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Content Based Routing > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Kurt Stam > Priority: Critical > Fix For: 4.2 Milestone Release 2 > > > For CBR, it currently has no exception handling. -- 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

17 years

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-486) Can ContentBasedRouter and StaticRouter "splt" based on an action property, verses using a different action "process" method?

by Tom Fennelly (JIRA)

Can ContentBasedRouter and StaticRouter "splt" 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: Mark Little Priority: Minor Fix For: 4.2 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

17 years

2
5
0 / 0

[JBoss JIRA] Work started: (JBESB-418) Catch-All/Otherwise/Default for CBR

by Kurt Stam (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-418?page=all ] Work on JBESB-418 started by Kurt Stam. > Catch-All/Otherwise/Default for CBR > ----------------------------------- > > Key: JBESB-418 > URL: http://jira.jboss.com/jira/browse/JBESB-418 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Content Based Routing > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Kurt Stam > Priority: Critical > Fix For: 4.2 Milestone Release 2 > > > For CBR, it currently has no exception handling. -- 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

17 years, 1 month

1
0
0 / 0

← Newer
1
...
14
15
16
17
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues April 2007