[jboss-dev-forums] [Design of POJO Server] - Re: Hot deploying deployers - deployer chains

[adrian@jboss.org]

"scott.stark at jboss.org" wrote : First, I'm not in agreement that hot deployment of deployers is needed. The only post bootstrap configuration I can see are aspects on the deployers themselves, but this can be a function of an individual deployment, not neccessarily a reconfiguration of the deployer.
  | 

I'm not sure I understand this.

What we are talking about will end up in the full solution as
a profile that looks like:

* kernel/profile/bootstrap
This will be semi-hardwired and represents a minimal set
of features to get the thing working (not what we have now).

* core configuration
These will be plugins, to the above, that need to be done early. 

Of course ideally we want as much as possible to be done
through deployers.

Thing that fall into this category:
aop-mc-int
profile plugins, e.g. JBoss ON integration
legacy jmx kernel
core logging (user configurable like conf/log4j.xml) 

* deployers
A set of deployer packages that plugin to the main deployer/profile.

* the deployments
A fixed list, scanner based, something else or a mixture.

So basically, I don't believe the MainDeployer/deployers
should be a part of the bootstrap configuration and that
there will be some form of "hotdeployment" even if it
is the initial step that creates a fixed list 
before the real deployments are done.

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

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