[jboss-user] [Microcontainer] - Re: ClassLoaderMetaData not propagating (yet?) to classloade
"gcompienne" wrote : It is due to the fact the code uses the "Module.domain" attribute rather than the "Module.metadata.domain". | I don't really understand what you mean here? The Module, Domain, ... is currently being rewritten, but it's probably gonna take till CR1 to put it in place. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4131012#4131012 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4131012 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Re: ClassLoaderMetaData not propagating (yet?) to classloade
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. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129735#4129735 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129735 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Re: ClassLoaderMetaData not propagating (yet?) to classloade
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). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129364#4129364 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129364 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Re: ClassLoaderMetaData not propagating (yet?) to classloade
"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
|{
|}
| }
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129275#4129275
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129275
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Re: ClassLoaderMetaData not propagating (yet?) to classloade
What makes me wonder if VFSTopLevelClassLoaderSystemDeployer is called is
because it declares that it needs a ClassLoaderFactory as input.
anonymous wrote :
| [DeployersImpl] Added deployer [EMAIL PROTECTED] for stage ClassLoader
| [EMAIL PROTECTED], org.jboss.deployers.structure.spi.ClassLoaderFactory]
outputs=[]}
| [EMAIL PROTECTED] outputs=[]}
| [EMAIL PROTECTED] outputs=[]}
|
And when my classloader is called, just before
VFSTopLevelClassLoaderSystemDeployer would be called, it shows me that no
ClassLoaderFactory attachment is available...
anonymous wrote :
| [TestClassloaderDeployer] ClassLoaderFactory not present...
| [TestClassloaderDeployer] ClassLoader not present...
| [BaseClassLoader] Created [EMAIL
PROTECTED]:/C:/jboss5-beta4/jboss-5.0.0.Beta4/server/default/deploy/apptest.jar}
with policy [EMAIL PROTECTED] [EMAIL PROTECTED]/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/],
[EMAIL PROTECTED] 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] [EMAIL PROTECTED]
registerClassLoader [EMAIL PROTECTED]@b3f6c2{domain=null [EMAIL
PROTECTED]/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/],
[EMAIL PROTECTED] 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... ;-)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129222#4129222
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129222
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Re: ClassLoaderMetaData not propagating (yet?) to classloade
"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. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129180#4129180 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129180 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Re: ClassLoaderMetaData not propagating (yet?) to classloade
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). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129166#4129166 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129166 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Re: ClassLoaderMetaData not propagating (yet?) to classloade
"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. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129144#4129144 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129144 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Re: ClassLoaderMetaData not propagating (yet?) to classloade
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). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129142#4129142 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129142 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Re: ClassLoaderMetaData not propagating (yet?) to classloade
Ok, Thanks :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129125#4129125 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129125 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Re: ClassLoaderMetaData not propagating (yet?) to classloade
Go get AS5 Beta4, it's out! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129123#4129123 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129123 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Re: ClassLoaderMetaData not propagating (yet?) to classloade
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... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129077#4129077 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129077 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Re: ClassLoaderMetaData not propagating (yet?) to classloade
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 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128922#4128922 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128922 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [Microcontainer] - Re: ClassLoaderMetaData not propagating (yet?) to classloade
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: [EMAIL PROTECTED]
| [TestDescribeDeployer] TestDescribeDeployer deploy called...
| [TestDescribeDeployer] ** ClassLoaderMetaData = [EMAIL PROTECTED]
| [TestDescribeDeployer] ** Name =
vfsfile:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar
| [TestDescribeDeployer] ** Domain =
| [TestDescribeDeployer] ** Parent Domain = null
| [TestDescribeDeployer] ** isImportAll? true
| [TestDescribeDeployer] ** Export all = NON_EMPTY
| [TestDescribeDeployer] ClassLoaderFactory not present...
| [TestDescribeDeployer] ParserMetaData found: [EMAIL PROTECTED]
| [TestDescribeDeployer] ** ClassLoaderMetaData = [EMAIL PROTECTED]
| [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 [EMAIL PROTECTED] with policy [EMAIL PROTECTED]
[EMAIL PROTECTED]/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/],
[EMAIL PROTECTED] context=vfsmemory://5c4o1e5d-iof0j2-fckddmwn-1-fckdgjxg-1l
real=vfsmemory://5c4o1e5d-iof0j2-fckddmwn-1-fckdgjxg-1l/classes]] delegates=[]
exported=[testapp]NON_EMPTY}
| [BaseClassLoaderDomain] [EMAIL PROTECTED]} registerClassLoader
[EMAIL PROTECTED]@aaff99{domain=null [EMAIL PROTECTED]/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/],
[EMAIL PROTECTED] context=vfsmemory://5c4o1e5d-iof0j2-fckddmwn-1-fckdgjxg-1l
real=vfsmemory://5c4o1e5d-iof0j2-fckddmwn-1-fckdgjxg-1l/classes]] delegates=[]
exported=[testapp]NON_EMPTY}}
| [TestClassloaderDeployer] ** ClassLoaderMetaData = [EMAIL PROTECTED]
| [TestClassloaderDeployer] ** Name =
vfsfile:/C:/jboss5-beta3/jboss-5.0.0.Beta3/server/default/deploy/apptest.jar
| [TestClassloaderDeployer] **
[jboss-user] [Microcontainer] - Re: ClassLoaderMetaData not propagating (yet?) to classloade
"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 = | | 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. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4128148#4128148 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4128148 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
