[
https://issues.apache.org/jira/browse/ARIES-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761577#action_12761577
]
Alan Cabrera commented on ARIES-12:
-----------------------------------
I don't believe that this is true. It explicitly states "That is, all
listeners must be notified before the Blueprint Container continues to the next
step.". The core spec also uses the language of synchronous delivery for
synchronous bundle listeners which we know the events get delivered before the
framework continues.
There is also other language in the core spec that discusses that it's ok to
asynchronously deliver messages to "regular" bundle listeners so long as the
order of the events is maintained. This is the behavior to which you speak
above. That language does not refer to such delivery as synchronous.
> 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.
