[jboss-dev-forums] [Design of POJO Server] - Re: Ordering of nested deployments

[adrian@jboss.org]

The component deployers split up a deployment into components
so the real deployers are easier to write (they just deal with one component).

It should probably be around 7000

e.g. 
-serivce.xml (ServiceDeploymentMetaData) is split into mbeans (ServiceMetaData)
-beans.xml (KernelDeployment) is split into pojos (BeanMetaData)
etc.

Also other deployers can target your real deployer at the atomic
level. e.g. the RARDeployer creates a ServiceMetaData (mbean for the rar)
without having to go through the full ServiceDeployment stuff.
I'd imagine you could do something similar with AOP if you
had a custom deployer that wanted to create a simple aspect
not the full -aop.xml

It makes it possible to write simple deployers that can do
things at the most atomic level with the metadata without having
to understand how to iterate.

Finally, it makes the real deployers less error prone since the
MainDeployer knows how to correctly unwind a failed deployment
if one of the components fails.

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

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