[cdi-dev] [JBoss JIRA] (CDI-548) FireAsyncException conflicting with CompletionStage definition

Tomas Remes (JIRA) issues at jboss.org
Wed Dec 16 08:30:00 EST 2015

    [ https://issues.jboss.org/browse/CDI-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141848#comment-13141848 ] 

Tomas Remes commented on CDI-548:

This could be marked as resolved since FireAsyncException has been removed. 

> FireAsyncException conflicting with CompletionStage definition
> --------------------------------------------------------------
>                 Key: CDI-548
>                 URL: https://issues.jboss.org/browse/CDI-548
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>          Components: Events
>    Affects Versions: 2.0-EDR1
>            Reporter: Jozef Hartinger
> CompletionStage documentation says:
> {quote}
> if a stage's computation terminates abruptly with an (unchecked) exception or error, then all dependent stages requiring its completion complete exceptionally as well, with a {@link CompletionException} holding the exception as its cause.
> {quote}
> On the other hand, the CDI spec suggests that if an observer notification fails, the CompletionStage fails with FireAsyncException directly (not wrapped within CompletionException). This creates a conflict as the CDI spec uses the CompletionStage API without fully conforming to its contract.

This message was sent by Atlassian JIRA

More information about the cdi-dev mailing list