You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Jeremy Hughes (JIRA)" <ji...@apache.org> on 2010/02/24 18:04:28 UTC

[jira] Updated: (ARIES-12) BlueprintListener events are not delivered synchronously and bad/tardy listeners are not ignored

     [ https://issues.apache.org/jira/browse/ARIES-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeremy Hughes updated ARIES-12:
-------------------------------

    Fix Version/s:     (was: 1.0)
                   0.1

> BlueprintListener events are not delivered synchronously and bad/tardy listeners are not ignored
> ------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-12
>                 URL: https://issues.apache.org/jira/browse/ARIES-12
>             Project: Aries
>          Issue Type: Bug
>          Components: Blueprint
>            Reporter: Rick McGuire
>            Assignee: Alan Cabrera
>             Fix For: 0.1
>
>
> The spec states that the events must be delivered synchronously. "These events are send synchronously with their cause. That is, all listeners must be notified before the Blueprint Container continues to the next step." So we must not use a thread pool to deliver.
> It also states "Blueprint Listener services that throw Exceptions or do not return in a reasonable time as judged by the Blueprint extender implementation, should be logged, if possible, and further ignored." We don't do this.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.