You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Alan Cabrera (JIRA)" <ji...@apache.org> on 2009/10/02 15:42:23 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 ]

Alan Cabrera updated ARIES-12:
------------------------------

    Summary: BlueprintListener events are not delivered synchronously and bad/tardy listeners are not ignored  (was: BlueprintListener events are not delivered synchronously)

> 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
>
> Section 121.12 of the blueprint specification has a requirement that blueprint events be delivered to BlueprintListener.blueprintEvent() methods.  However, the implementation of the event dispatcher submits the callbacks for each event to an executor for processing, leading to race conditions where events can be delivered out of order.  These events really should be placed on a queue and all callbacks completely processed in order. 

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