[
https://issues.jboss.org/browse/CDI-542?page=com.atlassian.jira.plugin.sy...
]
Antoine Sabot-Durand commented on CDI-542:
------------------------------------------
Don't panic Tomas, nobody read the spec ;).
More seriously, you're right, what I propose is to link the observer resolution
section to fire and fireasync section.
Regarding the second point it has been corrected with CDI-564
"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)