[
https://issues.apache.org/jira/browse/OWB-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784817#action_12784817
]
Mark Struberg commented on OWB-184:
-----------------------------------
after further debugging it turned out that we already deploy the
BeanManagerBean in
BeansDeployer#configureDefaultBeans()
My problem seems to be a undeploy issue:
{noformat}
ObserverMethodImpl<T>.getMethodArguments(Object) line: 271
ObserverMethodImpl<T>.notify(T) line: 188
NotificationManager.fireEvent(Object, Annotation...) line: 239
BeanManagerImpl.fireEvent(Object, Annotation...) line: 302
EnterpriseLifeCycle.applicationEnded(Object) line: 218
StandaloneContainersImpl.undeploy() line: 144
{noformat}
just a gut feeling:
Bean<?> bean = InjectionResolver.getInstance().implResolveByType(type,
bindingTypes).iterator().next();
doesn't find the BeanManagerBean anymore, because it seems to be be terminated
already...
> 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.
