[jboss-dev-forums] [Design of POJO Server] - Re: Integrating aop-mc-int bean metadata with AS5

[adrian@jboss.org]

"kabir.khan at jboss.com" wrote : 
  | As part of PreInstallAction, AbstractScopeInfo.addMetaData() adds a new MemoryMetaDataLoader under: 
  | 
  |   | [APPLICATION=vfszip:/Users/kabir/sourcecontrol/jboss-head/testsuite/output/lib/aop-scopeddependency-scoped.sar]
  |   | 
  | with this code
  | 
  |   | public void addMetaData(MutableMetaDataRepository repository, ControllerContext context)
  |   |    {
  |   |       this.repository = repository;
  |   |       ScopeKey scope = getMutableScope();
  |   |       MemoryMetaDataLoader mutable = new MemoryMetaDataLoader(scope);
  |   |       repository.addMetaDataRetrieval(mutable);
  |   |       addMetaData(repository, context, mutable);
  |   |    }
  |   | 
  | This happens for every bean, and it overwrites the existing MetaDataContext that contained the aspect manager to use, so this no longer exists in the repository. Should this check if a retrieval exists already, and add to that instead? 
  | 

Ok, so that's a bug. It shouldn't be overridding the mutable metadata context
if it already exists in the repository.

You're seeing it because you're using the wrong scope,
(the application instead of the instance scope) as the mutable scope,
but its obviously a problem if somebody wants to setup the instance
scope in the deployers.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169533#4169533

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169533