> Universal deployer is asked to deploy a package.

=)

> It starts by unpacking all the nested jars (recursively) and locating all
> the deployment descriptors (this functionality is pretty much in
> DeployerMBeanSupport today). (there may be some needs to ignore some dd's,
> per j2ee spec.  I'm still looking)
> 
> It then collects related deployment descriptors (such as ejb-jar.xml,
> jboss.xml, and jbosscmp.xml) and uses xslt to combine them into one jboss
> specific dd that includes all relevant info (this may include expanding
> defaults to be present wherever they are used). (I've prototyped this, its
> pretty easy. The ability to deploy from such a single dd has been
> requested).

Would this allow users to override specific parts of an ejb config perhaps?  
Say to just set (or unset) the default RMI port, or up the number of threads 
that a MDB is allocated?

> One of the features of the combined dd is that everything is an mbean
> configuration.  Therefore, there are no more standalone "deployer" mbeans. 
> Instead, an mbean that represents the deployed unit is created, and is
> responsible for interpreting the dd xml itself.  As a side effect, Andreas
> gets appropriately named mbeans for each deployment unit, that can create
> his jsr-77 mbeans to proxy themselves.

Will these beans have controls to allow them to be undeployed or changed at 
runtime too?

How will new deployment types be handled?  How does the universal deployer 
know what type of deployer mbean to create for the requested deployment 
unit?

Sounds like you might need a DeployerFactory, which despenses Deployers for 
the UniveralDeployer.  Or I guess the UD could also be a DF... 

If the new deployer concept will also manage the state and configuration of 
the deployment, perhaps it should be renamed for clarity?

--jason


> Note that the ConnectionFactoryLoader is kind of like this already -- it
> can be thought of an mbean that represents the deployment of a
> ConnectionFactory.  The RARDeployement is similar, but is not yet
> self-deploying: it is created by the (now almost empty) RARDeployer MBean.
> 
> Any thoughts?
> 
> david jencks
> 
> 
> 
> On 2001.12.10 16:19:46 -0500 Jason Dillon wrote:
> > Any chance this overhaul will introduce a single entry point to
> > deploy/undeploy?  By that I mean that it will have a collection of
> > mappings from url regex or something to the JMX object name of the actual
> > deployer that can handle those deployments.  Then all other components
> > will use that deployer controller.
> > 
> > I was looking to trim down the logging that is done for deploy/undeploy,
> > which I did some, but it is difficult since different components use
> > different deployers to get the job done.
> > 
> > It would be nice if there one a single place which would have the
> > authority to say if something was deployed or undeployed.
> > 
> > I was thinking a simple MBean which took a regex and an object name, then
> > simply proxied requests to the appropriate MBean as they came in....
> > nothing too fancy, or rather heavy.
> > 
> > --jason
> > 
> > ______________________________________________________________________
> > View this jboss-dev thread in the online forums:
> > http://jboss.org/forums/thread.jsp?forum=66&thread=5265
> > 
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-development
> > 
> > 
> 
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-development
> 


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to