[jboss-dev-forums] [Design of AOP on JBoss (Aspects/JBoss)] - ClassLoading Module usage

[kabir.khan@jboss.com]

As discussed in Neuchatel last week, I will make the first iteration of the scoped aop stuff work on the new classloaders, using the Module hack for now, and upgrade to use metadata later.

But when I deploy a sar with the following jboss-service.xml

  | <?xml version="1.0" encoding="UTF-8"?>
  | <server>
  |    <loader-repository>
  |    	aop.loading:loader=scope1
  |    </loader-repository>
  | 	<mbean code="org.jboss.test.aop.scoped.ScopedTester" name="jboss.aop:name=ScopedTester1">
  | 	   <attribute name="ExpectedInterceptorValue">11</attribute>
  | 	   <attribute name="ExpectedAspectValue">21</attribute>
  | 	   <attribute name="MetadataSuffix">1</attribute>
  | 	</mbean>
  | </server>
  | 
I don't seem to get any special information from the module?


  |    private ClassLoader getScopedClassLoader(VFSDeploymentUnit unit)
  |    {
  |       ...
  |       Module module = unit.getAttachment(Module.class);
  |       ...
  |       String domainName = module.getDomainName();
  |       ClassLoaderMetaData cmd = module.getMetadata();
  | //      boolean parentDelegation = cmd.isJ2seClassLoadingCompliance();
  |       
  |       System.out.println("****** DomainName: " + domainName + " parentDomain: " + module.getParentDomain());
  |    }
  | 
just gives

  | [STDOUT] ****** DomainName: <DEFAULT> parentDomain: null
  | 

Should I be using something other than the Domain/parentDomain, or is this broken somehow in ASS trunk?

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

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