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

Gerhard Petracek (JIRA) jira-events at lists.jboss.org
Sat Apr 27 07:41:53 EDT 2013

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

Gerhard Petracek commented on CDI-369:

created here, because a clear rule for checking it should be part of the specification
> 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
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the cdi-dev mailing list