[jira] Resolved: (OWB-184) BeanManager itself needs to be added as managed bean

["Mark Struberg (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OWB-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Struberg resolved OWB-184.
-------------------------------

    Resolution: Fixed

The problem which caused a lot TCKs to got skipped was that the BeanManager
got only added with configureDefaultBeans() at the end of the container startup.
If there was a DeploymentException or any similar unexpedted behaviour detected,
the BeanManager never got added as managed bean, thus causing an Exception
while firing the ShutdownEven.

> BeanManager itself needs to be added as managed bean
> ----------------------------------------------------
>
>                 Key: OWB-184
>                 URL: https://issues.apache.org/jira/browse/OWB-184
>             Project: OpenWebBeans
>          Issue Type: Bug
>    Affects Versions: M3
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>             Fix For: M4
>
>
> The BeanManager itself needs to be added as manages bean at the time we bootstrap the lifecycle.
> This needs to be done to be able to @Inject BeanManager bm; which a lot TCK tests rely on.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.