PHILOSOPHY
I'd say you mostly got it correct Bob.
The part you are missing is actually the most important part.
The Deployers create components, i.e. metadata for MBeans and POJOs
(or other component models).
They don't directly create anything, deployers are about MetaData processing.
Instead
[EMAIL PROTECTED] wrote :
| 1) META-INF/jboss-classloading.xml (PARSE STAGE)
|
It can also come from
| loader-repository/
|
configurations for backwards compability with jboss-3/4.x
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4178375#4178375
I see you completely dropped WCLD.
Perhaps you could still leave it,
and just mention that its sole purpose is to create web/war compatible CLMD.
Note: TomcatDeployer is not the last depolyer in this chain. ;-)
Check AbstractWarDeployer::deployWebModule,
where we create ServiceMetaData,
hence
Is each phase handled by a different deployer? For example, in the blog:
anonymous wrote : One of the earliest stages is the PARSE stage. For normal WAR
deployment, the WebAppParsingDeployer does exactly that.
|
| As the container enters the CLASSLOADER stage of deployment, normally the
Yes, each Deployer implementation calls setStage(...) to indicate which stage
of deployment it should be considered a candidate. There's a variety of base
deployers you can build from, which imply the stage. For instance, there's
AbstractParsingDeployer which sets the stage to PARSE. Then
As I re-read the post and the code...
WarClassLoaderDeployer actually is bound to POST_PARSE, which occurs after the
PARSE stage, but before the CLASSLOADER stage. So it's not always obvious
where things are firing by the class name alone.
I'll work on updating the blog-post as I continue to
I've updated it slightly and attached a newer diagram:
http://www.fnokd.com/2008/09/17/deployers-in-jboss-microcontainer/
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4177203#4177203
Reply to the post :
