[cdi-dev] [JBoss JIRA] (CDI-369) check required by #testFireEventWithNonRuntimeBindingTypeFails is too late

Martin Kouba (JIRA) issues at jboss.org
Thu Mar 30 09:16:00 EDT 2017

     [ https://issues.jboss.org/browse/CDI-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Kouba updated CDI-369:
    Fix Version/s: 2.1 (Discussion)

> check required by #testFireEventWithNonRuntimeBindingTypeFails is too late
> --------------------------------------------------------------------------
>                 Key: CDI-369
>                 URL: https://issues.jboss.org/browse/CDI-369
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Events
>    Affects Versions: 1.0
>            Reporter: Gerhard Petracek
>             Fix For: 2.1 (Discussion)
> as discussed with pete this ticket is based on https://issues.apache.org/jira/browse/OWB-798
> the check needed to pass  org.jboss.jsr299.tck.tests.event.bindingTypes.EventBindingTypesTest#testFireEventWithNonRuntimeBindingTypeFails is slow and even more important too late.
> we can do the same check (once) during bootstrapping before adding an observer. 
> reason why we don't need this check after bootstrapping: 
> if an invalid event (with an invalid qualifier) is used in a dyn. #fire, we can ignore the invalid literal-instance, because there is no corresponding observer (qualifiers of the observers would be checked during bootstrapping -> the startup would fail, if there is such an invalid observer).

This message was sent by Atlassian JIRA

More information about the cdi-dev mailing list