1 2 Previous Next 15 Replies Latest reply on Feb 21, 2008 4:55 AM by Ales Justin

    ClassLoaderMetaData not propagating (yet?) to classloader cr

    Gilles Compienne Newbie

      Sorry, last question for today.

      I am doing further testing with the deployers and I have noticed that the ClassLoaderMetaData info does not seem to be used (or fully used?) yet by the subsystem that triggers the creation of the classloader.

      In my describe stage I try to change the domain (to see a little what are the effects) and I can see that my classloader stage got the changes but for some reason the classloader that was created is still using the default domain.

      Any idea what I could be doing wrong?

      Here is the log I got:

      2008-02-08 17:49:31,856 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Add deployment: vfsfile:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar
      2008-02-08 17:49:31,856 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Scheduling deployment: vfsfile:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar parent=null
      2008-02-08 17:49:31,856 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Deploying vfsfile:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar
      2008-02-08 17:49:31,856 DEBUG [protomcf.test.deployer.TestParserDeployer] TestDeployerParser parsing...
      2008-02-08 17:49:31,856 DEBUG [protomcf.test.deployer.TestParserDeployer] TestDeployerParser returning: ParserMetaData@10009199[testapp.BaseTestServlet]
      2008-02-08 17:49:31,856 DEBUG [protomcf.test.deployer.TestDescribeDeployer] TestDescribeDeployer deploy called...
      2008-02-08 17:49:31,856 DEBUG [protomcf.test.deployer.TestDescribeDeployer] ** ClassLoaderMetaData = org.jboss.deployers.structure.spi.classloading.ClassLoaderMetaData@78e67f
      2008-02-08 17:49:31,856 DEBUG [protomcf.test.deployer.TestDescribeDeployer] ** Name = vfsfile:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar
      2008-02-08 17:49:31,856 DEBUG [protomcf.test.deployer.TestDescribeDeployer] ** Domain = <DEFAULT>
      2008-02-08 17:49:31,856 DEBUG [protomcf.test.deployer.TestDescribeDeployer] ** Parent Domain = null
      2008-02-08 17:49:31,856 DEBUG [protomcf.test.deployer.TestDescribeDeployer] ** isImportAll? true
      2008-02-08 17:49:31,856 DEBUG [protomcf.test.deployer.TestDescribeDeployer] ** Export all = NON_EMPTY
      2008-02-08 17:49:31,856 DEBUG [protomcf.test.deployer.TestDescribeDeployer] ClassLoaderFactory not present...
      2008-02-08 17:49:31,856 DEBUG [protomcf.test.deployer.TestDescribeDeployer] ParserMetaData found: ParserMetaData@10009199[testapp.BaseTestServlet]
      2008-02-08 17:49:31,856 DEBUG [protomcf.test.deployer.TestDescribeDeployer] ** ClassLoaderMetaData = org.jboss.deployers.structure.spi.classloading.ClassLoaderMetaData@78e67f
      2008-02-08 17:49:31,856 DEBUG [protomcf.test.deployer.TestDescribeDeployer] ** Name = vfsfile:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar
      2008-02-08 17:49:31,871 DEBUG [protomcf.test.deployer.TestDescribeDeployer] ** Domain = TestAppDomain
      2008-02-08 17:49:31,871 DEBUG [protomcf.test.deployer.TestDescribeDeployer] ** Parent Domain = null
      2008-02-08 17:49:31,871 DEBUG [protomcf.test.deployer.TestDescribeDeployer] ** isImportAll? false
      2008-02-08 17:49:31,871 DEBUG [protomcf.test.deployer.TestDescribeDeployer] ** Export all = NON_EMPTY
      2008-02-08 17:49:31,871 DEBUG [org.jboss.classloader.spi.base.BaseClassLoader] Created BaseClassLoader@164a659 with policy VFSClassLoaderPolicy@e523ed{domain=null roots=[JarEntryHandler@32044257[path=apptest.jar/WEB-INF/classes context=file:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/ real=jar:file:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar!/WEB-INF/classes/], MemoryContextHandler@26854149[path=classes context=vfsmemory://5c4o1s-a5nrui-fcf14ibf-1-fcf19nbz-1l real=vfsmemory://5c4o1s-a5nrui-fcf14ibf-1-fcf19nbz-1l/classes]] delegates=[] exported=[testapp]NON_EMPTY}
      2008-02-08 17:49:31,871 DEBUG [org.jboss.classloader.spi.base.BaseClassLoaderDomain] ClassLoaderDomain@670479{<DEFAULT>} registerClassLoader BaseClassLoader@164a659{VFSClassLoaderPolicy@e523ed{domain=null roots=[JarEntryHandler@32044257[path=apptest.jar/WEB-INF/classes context=file:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/ real=jar:file:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar!/WEB-INF/classes/], MemoryContextHandler@26854149[path=classes context=vfsmemory://5c4o1s-a5nrui-fcf14ibf-1-fcf19nbz-1l real=vfsmemory://5c4o1s-a5nrui-fcf14ibf-1-fcf19nbz-1l/classes]] delegates=[] exported=[testapp]NON_EMPTY}}
      2008-02-08 17:49:31,871 DEBUG [protomcf.test.deployer.TestClassloaderDeployer] ** ClassLoaderMetaData = org.jboss.deployers.structure.spi.classloading.ClassLoaderMetaData@78e67f
      2008-02-08 17:49:31,871 DEBUG [protomcf.test.deployer.TestClassloaderDeployer] ** Name = vfsfile:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar
      2008-02-08 17:49:31,871 DEBUG [protomcf.test.deployer.TestClassloaderDeployer] ** Domain = TestAppDomain
      2008-02-08 17:49:31,871 DEBUG [protomcf.test.deployer.TestClassloaderDeployer] ** Parent Domain = null
      2008-02-08 17:49:31,871 DEBUG [protomcf.test.deployer.TestClassloaderDeployer] ** isImportAll? false
      2008-02-08 17:49:31,871 DEBUG [protomcf.test.deployer.TestClassloaderDeployer] ** Export all = NON_EMPTY
      2008-02-08 17:49:31,871 DEBUG [protomcf.test.deployer.TestClassloaderDeployer] ClassLoaderFactory not present...
      2008-02-08 17:49:31,871 DEBUG [protomcf.test.deployer.TestClassloaderDeployer] ClassLoader is BaseClassLoader@164a659
      2008-02-08 17:49:31,871 DEBUG [protomcf.test.deployer.TestClassloaderDeployer] ** module = org.jboss.deployers.plugins.classloading.Module@1d2822f
      2008-02-08 17:49:31,871 DEBUG [org.jboss.ejb3.deployers.Ejb3Deployer] ********* Ejb3Deployer Begin Unit: apptest.jar jar: apptest.jar
      2008-02-08 17:49:31,871 DEBUG [org.jboss.ejb3.Ejb3Deployment] EJB3 deployment time took: 0
      2008-02-08 17:49:31,871 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully Deployed vfsfile:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar
      
      


        • 1. Re: ClassLoaderMetaData not propagating (yet?) to classloade
          Ales Justin Master

           

          "gcompienne" wrote:

          I am doing further testing with the deployers and I have noticed that the ClassLoaderMetaData info does not seem to be used (or fully used?) yet by the subsystem that triggers the creation of the classloader.

          It's the ClassLoading class that uses CLMD.

          "gcompienne" wrote:

          2008-02-08 17:49:31,856 DEBUG [protomcf.test.deployer.TestDescribeDeployer] ** Domain = <DEFAULT>
          

          Looks like this is being used.
          You're probably not attaching the second CLMD into the attachments.

          I would need to see TestDescribeDeployer for more info.

          • 2. Re: ClassLoaderMetaData not propagating (yet?) to classloade
            Gilles Compienne Newbie

            Ok, here is the code for TestDescribeDeployer:

            package protomcf.test.deployer;
            
            import java.util.List;
            
            import org.jboss.deployers.spi.DeploymentException;
            import org.jboss.deployers.spi.deployer.DeploymentStages;
            import org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer;
            import org.jboss.deployers.structure.spi.ClassLoaderFactory;
            import org.jboss.deployers.structure.spi.DeploymentUnit;
            import org.jboss.deployers.structure.spi.classloading.ClassLoaderMetaData;
            import org.jboss.logging.Logger;
            
            import protomcf.test.metadata.ParserMetaData;
            
            public class TestDescribeDeployer extends AbstractRealDeployer {
            
             private final Logger log = Logger.getLogger(TestDescribeDeployer.class);
            
             public TestDescribeDeployer() {
             setStage(DeploymentStages.DESCRIBE);
             setInputs(new Class<?>[] {ParserMetaData.class, ClassLoaderMetaData.class});
             //setInput(ParserMetaData.class);
             //setInput(ClassLoaderMetaData.class);
             setOutput(ClassLoaderMetaData.class);
             //setOutput(TestMetaData.class);
             //setAllInputs(true);
             }
            
             @Override
             protected void internalDeploy(DeploymentUnit unit) throws DeploymentException {
             log.debug("TestDescribeDeployer deploy called...");
             ClassLoaderMetaData clmd = unit.getAttachment(
             ClassLoaderMetaData.class);
             if (clmd != null) {
             Utils.displayCLMetaData(clmd, log);
             }
             ClassLoaderFactory clf = unit.getAttachment(ClassLoaderFactory.class);
             if (clf != null) {
             log.debug("ClassLoaderFactory is " + clf);
             } else {
             log.debug("ClassLoaderFactory not present...");
             }
             ParserMetaData pmd = unit.getAttachment(ParserMetaData.class);
             if (pmd != null) {
             log.debug("ParserMetaData found: " + pmd);
             clmd.setDomain("TestAppDomain");
             clmd.setImportAll(false);
             Utils.displayCLMetaData(clmd, log);
             unit.addAttachment(ClassLoaderMetaData.class, clmd);
             } else {
             log.debug("ParserMetaData not present...");
             }
             }
            
            }
            


            Also here follows a more readable version of the log:

            [MainDeployerImpl] Add deployment: vfsfile:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar
            [MainDeployerImpl] Scheduling deployment: vfsfile:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar parent=null
            [DeployersImpl] Deploying vfsfile:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar
            [TestParserDeployer] TestDeployerParser parsing...
            [TestParserDeployer] TestDeployerParser returning: ParserMetaData@9674968[testapp.BaseTestServlet]
            [TestDescribeDeployer] TestDescribeDeployer deploy called...
            [TestDescribeDeployer] ** ClassLoaderMetaData = org.jboss.deployers.structure.spi.classloading.ClassLoaderMetaData@17a4a80
            [TestDescribeDeployer] ** Name = vfsfile:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar
            [TestDescribeDeployer] ** Domain = <DEFAULT>
            [TestDescribeDeployer] ** Parent Domain = null
            [TestDescribeDeployer] ** isImportAll? true
            [TestDescribeDeployer] ** Export all = NON_EMPTY
            [TestDescribeDeployer] ClassLoaderFactory not present...
            [TestDescribeDeployer] ParserMetaData found: ParserMetaData@9674968[testapp.BaseTestServlet]
            [TestDescribeDeployer] ** ClassLoaderMetaData = org.jboss.deployers.structure.spi.classloading.ClassLoaderMetaData@17a4a80
            [TestDescribeDeployer] ** Name = vfsfile:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar
            [TestDescribeDeployer] ** Domain = TestAppDomain
            [TestDescribeDeployer] ** Parent Domain = null
            [TestDescribeDeployer] ** isImportAll? false
            [TestDescribeDeployer] ** Export all = NON_EMPTY
            [BaseClassLoader] Created BaseClassLoader@1b152ad with policy VFSClassLoaderPolicy@aaff99{domain=null roots=[JarEntryHandler@26648165[path=apptest.jar/WEB-INF/classes context=file:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/ real=jar:file:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar!/WEB-INF/classes/], MemoryContextHandler@7525824[path=classes context=vfsmemory://5c4o1e5d-iof0j2-fckddmwn-1-fckdgjxg-1l real=vfsmemory://5c4o1e5d-iof0j2-fckddmwn-1-fckdgjxg-1l/classes]] delegates=[] exported=[testapp]NON_EMPTY}
            [BaseClassLoaderDomain] ClassLoaderDomain@12462b3{<DEFAULT>} registerClassLoader BaseClassLoader@1b152ad{VFSClassLoaderPolicy@aaff99{domain=null roots=[JarEntryHandler@26648165[path=apptest.jar/WEB-INF/classes context=file:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/ real=jar:file:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar!/WEB-INF/classes/], MemoryContextHandler@7525824[path=classes context=vfsmemory://5c4o1e5d-iof0j2-fckddmwn-1-fckdgjxg-1l real=vfsmemory://5c4o1e5d-iof0j2-fckddmwn-1-fckdgjxg-1l/classes]] delegates=[] exported=[testapp]NON_EMPTY}}
            [TestClassloaderDeployer] ** ClassLoaderMetaData = org.jboss.deployers.structure.spi.classloading.ClassLoaderMetaData@17a4a80
            [TestClassloaderDeployer] ** Name = vfsfile:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar
            [TestClassloaderDeployer] ** Domain = TestAppDomain
            [TestClassloaderDeployer] ** Parent Domain = null
            [TestClassloaderDeployer] ** isImportAll? false
            [TestClassloaderDeployer] ** Export all = NON_EMPTY
            [TestClassloaderDeployer] ClassLoaderFactory not present...
            [TestClassloaderDeployer] ClassLoader is BaseClassLoader@1b152ad
            [TestClassloaderDeployer] ** module = org.jboss.deployers.plugins.classloading.Module@12f5047
            [Ejb3Deployer] ********* Ejb3Deployer Begin Unit: apptest.jar jar: apptest.jar
            [Ejb3Deployment] EJB3 deployment time took: 0
            [DeployersImpl] Fully Deployed vfsfile:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar
            


            On the log, you can see that TestDescribeDeployer did set the domain to "TestAppDomain" and the TestClassloaderDeployer clearly pick that up.

            However on the two lines where the base class loader is created (in between the describe and CL deployer) we can clearly see that the domain is equal to default. I wonder what would also be the status of the "import" state but I can't display it yet (I will need to give it a go with a debugger at some point).

            Thanks for your help.

            Gilles.

            • 3. Re: ClassLoaderMetaData not propagating (yet?) to classloade
              Ales Justin Master

              What's the env you're running this?

              Can you check the trunk, and let me know what revision did you use if it's still failing

              • 4. Re: ClassLoaderMetaData not propagating (yet?) to classloade
                Gilles Compienne Newbie

                I am using JBoss AS 5 beta 3 (so MC beta 9) with the changes in the bootstrap config that activates the MC classloading mechanism.

                I tried to have the AS 5 beta 3 running with the trunk version of MC but it failed on startup...

                I will try at some point against a trunk of MC (although I will need to somehow bootstrap enough of it to have things like VFS) or perhaps against JBoss AS beta 4 when it comes out...

                • 7. Re: ClassLoaderMetaData not propagating (yet?) to classloade
                  Gilles Compienne Newbie

                  Ok, I just tried against JBoss AS 5 beta 4 and admittedly I am still having the same problem...

                  I also just realized that it must be some default classloader mechanism that must create the BaseClassLoader because in fact the VFSTopLevelClassLoaderSystemDeployer that has been deployed for the CLASSLOADER stage does not kick-in (as there is no ClassLoaderFactory input being presented).

                  • 8. Re: ClassLoaderMetaData not propagating (yet?) to classloade
                    Ales Justin Master

                     

                    "gcompienne" wrote:
                    Ok, Thanks :-)

                    :-)

                    We need to have the same env (at least AS5, MC, ...), so that we're really 'talking' about the same problem (if it's still there), and not just guessing. ;-)

                    • 9. Re: ClassLoaderMetaData not propagating (yet?) to classloade
                      Gilles Compienne Newbie

                      Ok, so is JBoss 5 beta 4 a reasonable test environment for this issue?

                      Or should I try and fit in it the latest MC trunk in it? (I mean, I can try but I am not sure I will succeed: I had a few issues when I tried that a few days ago with the trunk and AS 5 beta 3).

                      • 10. Re: ClassLoaderMetaData not propagating (yet?) to classloade
                        Ales Justin Master

                         

                        "gcompienne" wrote:
                        Ok, so is JBoss 5 beta 4 a reasonable test environment for this issue?

                        Beta4 is OK.

                        But I doubt that VFSTopLevelClassLoaderSystemDeployer is not kicking in.
                        The deployer itself is a CLFactory impl.
                        Perhaps you can modify this class to add more debugging.


                        • 11. Re: ClassLoaderMetaData not propagating (yet?) to classloade
                          Gilles Compienne Newbie

                          What makes me wonder if VFSTopLevelClassLoaderSystemDeployer is called is because it declares that it needs a ClassLoaderFactory as input.


                          [DeployersImpl] Added deployer protomcf.test.deployer.TestClassloaderDeployer@1b688c0 for stage ClassLoader
                          org.jboss.web.tomcat.service.deployers.WarClassLoaderDeployer@80bc28{inputs=[org.jboss.metadata.web.jboss.JBossWebMetaData, org.jboss.deployers.structure.spi.ClassLoaderFactory] outputs=[]}
                          protomcf.test.deployer.TestClassloaderDeployer@1b688c0{inputs=[] outputs=[]}
                          org.jboss.deployers.vfs.plugins.classloader.VFSTopLevelClassLoaderSystemDeployer@6c5356{inputs=[org.jboss.deployers.structure.spi.ClassLoaderFactory] outputs=[]}


                          And when my classloader is called, just before VFSTopLevelClassLoaderSystemDeployer would be called, it shows me that no ClassLoaderFactory attachment is available...



                          [TestClassloaderDeployer] ClassLoaderFactory not present...
                          [TestClassloaderDeployer] ClassLoader not present...
                          [BaseClassLoader] Created BaseClassLoader@f157b0{vfsfile:/C:/jboss5-beta4/jboss-5.0.0.Beta4/server/default/deploy/apptest.jar} with policy VFSClassLoaderPolicy@b3f6c2{domain=null roots=[JarEntryHandler@17656871[path=apptest.jar/WEB-INF/classes context=file:/C:/jboss5-beta4/jboss-5.0.0.Beta4/server/default/deploy/ real=jar:file:/C:/jboss5-beta4/jboss-5.0.0.Beta4/server/default/deploy/apptest.jar!/WEB-INF/classes/], MemoryContextHandler@3643618[path=classes context=vfsmemory://5c4o1e5d-bqyidg-fcm2qgcx-1-fcm46gz5-1m real=vfsmemory://5c4o1e5d-bqyidg-fcm2qgcx-1-fcm46gz5-1m/classes]] delegates=[] exported=[testapp]NON_EMPTY}
                          2008-02-13 16:45:25,760 DEBUG [org.jboss.classloader.spi.base.BaseClassLoaderDomain] ClassLoaderDomain@1c09624{<DEFAULT>} registerClassLoader BaseClassLoader@f157b0{VFSClassLoaderPolicy@b3f6c2{domain=null roots=[JarEntryHandler@17656871[path=apptest.jar/WEB-INF/classes context=file:/C:/jboss5-beta4/jboss-5.0.0.Beta4/server/default/deploy/ real=jar:file:/C:/jboss5-beta4/jboss-5.0.0.Beta4/server/default/deploy/apptest.jar!/WEB-INF/classes/], MemoryContextHandler@3643618[path=classes context=vfsmemory://5c4o1e5d-bqyidg-fcm2qgcx-1-fcm46gz5-1m real=vfsmemory://5c4o1e5d-bqyidg-fcm2qgcx-1-fcm46gz5-1m/classes]] delegates=[] exported=[testapp]NON_EMPTY}}


                          I am going to hack VFSTopLevelClassLoaderSystemDeployer to try and understand what's happening but admittedly I am little puzzled... ;-)

                          • 12. Re: ClassLoaderMetaData not propagating (yet?) to classloade
                            Ales Justin Master

                             

                            "gcompienne" wrote:

                            And when my classloader is called, just before VFSTopLevelClassLoaderSystemDeployer would be called, it shows me that no ClassLoaderFactory attachment is available...

                            public abstract class AbstractClassLoaderDeployer extends AbstractDeployer implements ClassLoaderFactory
                            {
                             /**
                             * Create a new AbstractClassLoaderDeployer.
                             */
                             public AbstractClassLoaderDeployer()
                             {
                             setStage(DeploymentStages.CLASSLOADER);
                             setInput(ClassLoaderFactory.class);
                             setAllInputs(true);
                             }
                            
                             public void deploy(DeploymentUnit unit) throws DeploymentException
                             {
                             ClassLoaderFactory factory = unit.getAttachment(ClassLoaderFactory.class);
                             if (factory == null)
                             factory = this;
                             unit.createClassLoader(factory);
                             }
                            
                             public void undeploy(DeploymentUnit unit)
                             {
                             ClassLoaderFactory factory = unit.getAttachment(ClassLoaderFactory.class);
                             if (factory == null)
                             factory = this;
                             unit.removeClassLoader(factory);
                             }
                            
                             public void removeClassLoader(DeploymentContext context) throws Exception
                             {
                             }
                            }
                            


                            • 13. Re: ClassLoaderMetaData not propagating (yet?) to classloade
                              Gilles Compienne Newbie

                              Yes, I saw the code you refer to. But that's what got me puzzled:

                              I suspect you are refering to the fact that, if there is no ClassLoaderFactory, then it will automatically create one (as VFSTopLevelClassLoaderSystemDeployer is a decendant of AbstractClassLoaderDeployer).

                              But still, before the system gets there, a ClassLoaderFactory input should be present before this deployer can get selected (as it is a required input).

                              But now I am realizing that I have perhaps missed something: The "setAllInputs(true)".

                              When "setAllInputs(true)" is combined with a setInput, does it mean that the input becomes optional? (I wondered in an earlier post if the setAllInput simply override the inputs as being "all inputs" but I now suspect that is not the case and that it just change the inputs from a "required" state to an "optional" one). This would explain why VFSTopLevelClassLoaderSystemDeployer is called whilst the required input is not there... Is my understanding now correct?

                              What's also interesting and perhaps misleading is the fact that when inputs are reported on the log the "setAllInputs" status is probably not shown (it just shows the expected inputs, whatever they end up being required or optional).

                              • 14. Re: ClassLoaderMetaData not propagating (yet?) to classloade
                                Gilles Compienne Newbie

                                Ok, I think I found out why changing the domain on the ClassLoaderMetaData didn't propagate to the created classloader. It is due to the fact the code uses the "Module.domain" attribute rather than the "Module.metadata.domain".

                                All the other information seems to propagate fine.

                                I will try to access and change the "Module.domain" from the deployer but I wonder if I didn't misunderstood what the domain was for...

                                Initially I was thinking of it as a nice way (via CLMetaData) to try and link related areas together (like all the classloaders of a specific app) but I am not sure anymore if that's really the case.

                                1 2 Previous Next