aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niclas Hedhman (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ARIES-12) BlueprintListener events are not delivered synchronously and bad/tardy listeners are not ignored
Date Sat, 03 Oct 2009 05:11:23 GMT

    [ https://issues.apache.org/jira/browse/ARIES-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761808#action_12761808
] 

Niclas Hedhman commented on ARIES-12:
-------------------------------------

I agree with Alan's assessment here. The OSGi specs are very explicit when it comes to event
delievery. 
I can agree with Rick that I don't understand why the text says it must be synchronously,
though, but that is a lost battle by now.

> 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
>
> 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.


Mime
View raw message