[jboss-user] [JBoss Microcontainer] - Re: More on BaseClassLoader conflict with Instrumentation....

Ales Justin do-not-reply at jboss.com
Wed Feb 23 09:28:57 EST 2011

Ales Justin [http://community.jboss.org/people/alesj] created the discussion

"Re: More on BaseClassLoader conflict with Instrumentation...."

To view the discussion, visit: http://community.jboss.org/message/589278#589278

All deployments are metadata / attachment driven via deployers.
What this means in more human form? :-)
btw: did you read any of the DZone article's on Microcontainer topic?

Each configuration file is transfomed into some metadata class / instance.
And this metadata instance is added / attached to DeploymentUnit instance.
DeploymentUnit is what is passed between deployer instances -- see Deployer::deploy(DeploymentUnit unit).
DeploymentUnit's attachments are nothing more then a smarter semi type-safe Map.
As you can see deployers actually don't care where this metadata instances come from.
It could be either from parsed configuration or added programatically.

So, to answer your question, yes it can be done programmatically.
Simply add a new custom deployer to the existing chain of deployers.
Where you would add or replace or modify an existing ClassLoaderMetaData, which is jboss-classloading.xml is parsed into.

Reply to this message by going to Community

Start a new discussion in JBoss Microcontainer at Community

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20110223/2d7d4cd2/attachment.html 

More information about the jboss-user mailing list