]
Adrian Brock updated JBMICROCONT-330:
-------------------------------------
Component/s: Dependency
ScopeInfo should use the existing Mutable metadata if it already
exists
-----------------------------------------------------------------------
Key: JBMICROCONT-330
URL:
https://jira.jboss.org/jira/browse/JBMICROCONT-330
Project: JBoss MicroContainer
Issue Type: Bug
Components: Dependency
Reporter: Adrian Brock
Fix For: JBossMC.2.0.0.CR1
Currently the AbstractScopeInfo class is always creating a new Mutable MetaMeta context
within the MDR.
This would cause a problem where the scope has already been constructed, e.g. by the
deployers.
public void addMetaData(MutableMetaDataRepository repository, ControllerContext
context)
{
this.repository = repository;
ScopeKey scope = getMutableScope();
// Needs a check here for already exists - see the version of getMutableMetaData in
AbstractDeploymentContext
MemoryMetaDataLoader mutable = new MemoryMetaDataLoader(scope);
repository.addMetaDataRetrieval(mutable);
addMetaData(repository, context, mutable);
}
Similarly ScopeInfo::removeMetaData(), should not be removing MDR contexts it didn't
construct.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: