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

Tue May 1 06:34:30 EDT 2007

    [ 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