esb-issues May 2007

esb-issues@lists.jboss.org

1 participants
135 discussions

[JBoss JIRA] Created: (JBESB-495) Registry seems to be ignoring the service name in lookups

by Tom Fennelly (JIRA)

Registry seems to be ignoring the service name in lookups --------------------------------------------------------- Key: JBESB-495 URL: http://jira.jboss.com/jira/browse/JBESB-495 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.2 Milestone Release 1 Reporter: Tom Fennelly Assigned To: Mark Little Fix For: 4.2 Milestone Release 2 >From what I can see, it doesn't seem to matter what you put in for the service name. So, if I query for endpoints for service X:1, I'll get a list that includes endpoints for services X:2, X3 etc -- 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, 6 months

3
3
0 / 0

[JBoss JIRA] Closed: (JBESB-193) Need support for notification generatoin from within ActionProcessor.process method

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-193?page=all ] Mark Little closed JBESB-193. ----------------------------- Fix Version/s: 4.2 Milestone Release 2 (was: 4.2) Resolution: Done > Need support for notification generatoin from within ActionProcessor.process method > ----------------------------------------------------------------------------------- > > Key: JBESB-193 > URL: http://jira.jboss.com/jira/browse/JBESB-193 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 > Reporter: Tom Fennelly > Assigned To: Mark Little > Fix For: 4.2 Milestone Release 2 > > Time Spent: 3 hours > Remaining Estimate: 0 minutes > > In version 4.0, the Action Processing pipeline management code raises notifications in response to an exception from the ActionProcessor.process method. The pipeline managemnt code calls the getOkNotification (no exception) or getErrorNotification (exception) to get the notification message. > For many reasons, this is a very flawed model. Notifications should be raised from within the process method by means of attaching the notifications (error or otherwise) to the message (the mechanism is a design issue). Once the process method returns, the pipline processing management code can check the message for notifications. If there are errors, it can/should (?) abort the message processing, send the error notification (by whatever notification options are configured on the listener) and signal the failure to the calling process (by whatever failure config is configured on the listener). > The getOk and getErro methods can then be removed. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-193) Need support for notification generatoin from within ActionProcessor.process method

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-193?page=all ] Mark Little updated JBESB-193: ------------------------------ Affects Version/s: 4.0 (was: 5.0) > Need support for notification generatoin from within ActionProcessor.process method > ----------------------------------------------------------------------------------- > > Key: JBESB-193 > URL: http://jira.jboss.com/jira/browse/JBESB-193 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.0 > Reporter: Tom Fennelly > Assigned To: Mark Little > Fix For: 4.2 Milestone Release 2 > > Time Spent: 3 hours > Remaining Estimate: 0 minutes > > In version 4.0, the Action Processing pipeline management code raises notifications in response to an exception from the ActionProcessor.process method. The pipeline managemnt code calls the getOkNotification (no exception) or getErrorNotification (exception) to get the notification message. > For many reasons, this is a very flawed model. Notifications should be raised from within the process method by means of attaching the notifications (error or otherwise) to the message (the mechanism is a design issue). Once the process method returns, the pipline processing management code can check the message for notifications. If there are errors, it can/should (?) abort the message processing, send the error notification (by whatever notification options are configured on the listener) and signal the failure to the calling process (by whatever failure config is configured on the listener). > The getOk and getErro methods can then be removed. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Work logged: (JBESB-193) Need support for notification generatoin from within ActionProcessor.process method

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-193?page=worklog#action_12360990 ] Mark Little logged work on JBESB-193: ------------------------------------- Time Spent: 1 hour Time Spent: 3 hours (was: 2 hours) > Need support for notification generatoin from within ActionProcessor.process method > ----------------------------------------------------------------------------------- > > Key: JBESB-193 > URL: http://jira.jboss.com/jira/browse/JBESB-193 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 5.0 > Reporter: Tom Fennelly > Assigned To: Mark Little > Fix For: 4.2 > > Time Spent: 3 hours > Remaining Estimate: 0 minutes > > In version 4.0, the Action Processing pipeline management code raises notifications in response to an exception from the ActionProcessor.process method. The pipeline managemnt code calls the getOkNotification (no exception) or getErrorNotification (exception) to get the notification message. > For many reasons, this is a very flawed model. Notifications should be raised from within the process method by means of attaching the notifications (error or otherwise) to the message (the mechanism is a design issue). Once the process method returns, the pipline processing management code can check the message for notifications. If there are errors, it can/should (?) abort the message processing, send the error notification (by whatever notification options are configured on the listener) and signal the failure to the calling process (by whatever failure config is configured on the listener). > The getOk and getErro methods can then be removed. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-193) Need support for notification generatoin from within ActionProcessor.process method

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-193?page=comments#action_12360989 ] Mark Little commented on JBESB-193: ----------------------------------- Changed handling to use exceptions only in order not to break the new action chaining rules. > Need support for notification generatoin from within ActionProcessor.process method > ----------------------------------------------------------------------------------- > > Key: JBESB-193 > URL: http://jira.jboss.com/jira/browse/JBESB-193 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 5.0 > Reporter: Tom Fennelly > Assigned To: Mark Little > Fix For: 4.2 > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > In version 4.0, the Action Processing pipeline management code raises notifications in response to an exception from the ActionProcessor.process method. The pipeline managemnt code calls the getOkNotification (no exception) or getErrorNotification (exception) to get the notification message. > For many reasons, this is a very flawed model. Notifications should be raised from within the process method by means of attaching the notifications (error or otherwise) to the message (the mechanism is a design issue). Once the process method returns, the pipline processing management code can check the message for notifications. If there are errors, it can/should (?) abort the message processing, send the error notification (by whatever notification options are configured on the listener) and signal the failure to the calling process (by whatever failure config is configured on the listener). > The getOk and getErro methods can then be removed. -- 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, 6 months

1
0
0 / 0

← Newer
1
...
11
12
13
14
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues May 2007