[cdi-dev] [JBoss JIRA] (CDI-333) Treatment of exceptions raised during container lifecycle event notification inconsistent

[Pete Muir (JIRA)]

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

Pete Muir resolved CDI-333.
---------------------------

    Resolution: Done


Done
                
> Treatment of exceptions raised during container lifecycle event notification inconsistent
> -----------------------------------------------------------------------------------------
>
>                 Key: CDI-333
>                 URL: https://issues.jboss.org/browse/CDI-333
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Portable Extensions
>    Affects Versions: 1.1.PFD
>            Reporter: Jozef Hartinger
>            Assignee: Pete Muir
>             Fix For: 1.1.FD
>
>
> If an exception is raised by extension during container lifecycle event notification this exception is treated either as a definition or a deployment problem.
> Definition problems:
> * BeforeBeanDiscovery
> * AfterBeanDiscovery
> * ProcessAnnotatedType
> * ProcessInjectionPoint
> * ProcessInjectionTarget
> * ProcessProducer
> * ProcessBeanAttributes
> * ProcessBean
> * ProcessObserverMethod
> Deployment problems:
> * AfterTypeDiscovery
> * AfterDeploymentValidation
> AfterTypeDiscovery seems to be the odd one out as the event is fired between BBD and ABD which both treat extension exceptions as definition errors.

--
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