[cdi-dev] [JBoss JIRA] (CDI-542) "10.2.2. Firing events asynchronously" update/enhancements
Antoine Sabot-Durand (JIRA)
issues at jboss.org
Wed Nov 4 05:48:00 EST 2015
[ https://issues.jboss.org/browse/CDI-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Sabot-Durand updated CDI-542:
-------------------------------------
Fix Version/s: 2.0-EDR2
> "10.2.2. Firing events asynchronously" update/enhancements
> ----------------------------------------------------------
>
> Key: CDI-542
> URL: https://issues.jboss.org/browse/CDI-542
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Affects Versions: 2.0-EDR1
> Reporter: Tomas Remes
> Fix For: 2.0-EDR2
>
>
> This chapter (similar as the preceding) defines in general what does it mean to "fire an event" (sync vs async). Let say I am ordinary reader reading the spec from the beginning and I come to this chapter.
> First of all I guess I will struggle little bit with the notion of ??resolved synchronous observers?? (vs ??resolved asynchronous observers??)
> I think the following important information from "10.3. Observer resolution" could be mentioned earlier or some general description/example could be handy:
> {quote}
> * The event is fired synchronously and the observer is defined with @Observes.
> * The event is fired asynchronously and the observer is defined with @Observes or @ObservesAsync.
> {quote}
> Second there is following sentence which TBH I have had fairly hard times to understand:
> {quote}
> If synchronous observer have to be notified, fireAsync returns immediately after the last synchronous observer has returned. Otherwise it returns immediately.
> {quote}
> ...and is IMO wrong. There should be "observers have to be" or "observer has to be" and it could be bit more explanatory.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the cdi-dev
mailing list