[
https://jira.jboss.org/jira/browse/JBMICROCONT-333?page=com.atlassian.jir...
]
Ales Justin resolved JBMICROCONT-333.
-------------------------------------
Resolution: Partially Completed
Proper fix needs more complex solution, beyond the scoped controller issue.
This should be resolved in the next minor version.
Currently use workaround as exposed in fixed/hacked ScopingOverrideUnitTestCase.
ScopedControllerContexts are sharing metadata if they have the same
bean name
-----------------------------------------------------------------------------
Key: JBMICROCONT-333
URL:
https://jira.jboss.org/jira/browse/JBMICROCONT-333
Project: JBoss Microcontainer
Issue Type: Bug
Components: Kernel
Reporter: Adrian Brock
Assignee: Ales Justin
Fix For: JBossMC.2.0.0.CR1
See ScopingOverrideUnitTestCase
The first install of "simple" has annotations that say it should be scoped.
The second install of "simple" is picking up these annotations since they share
the same INSTANCE metadata
meaning it thinks it should also be scoped.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira