[
https://issues.jboss.org/browse/WFLY-2481?page=com.atlassian.jira.plugin....
]
Emond Papegaaij commented on WFLY-2481:
---------------------------------------
I don't know why this was moved to WildFly, but the same problem is also present in
Glassfish. I've updated the testcase to demonstrate the problem on both WildFly and
Glassfish.
CDI.current().getBeanManager() returns a beanmanager from a different
deployment
--------------------------------------------------------------------------------
Key: WFLY-2481
URL:
https://issues.jboss.org/browse/WFLY-2481
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: CDI / Weld
Affects Versions: 8.0.0.Beta1
Environment: WildFly master build
Reporter: Emond Papegaaij
Assignee: Jozef Hartinger
CDI.current().getBeanManager() uses the classname of the calling class to cache
BeanManagers returned. This fails if multiple deployments contain classes with the same
name. For example, wicket-cdi-1.1 looks up the BeanManager from
org.apache.wicket.cdi.CdiConfiguration. If multiple Wicket-CDI applications are deployed
in the same container, every BeanManager lookup will return the instance cached on the
first call.
--
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