On my proposal. I am saying:
1) SubDeployerSupport is too generic (deliberatly) since it allows things like
Tomcat deployments to be processed through it.
2) Ideally, deployments should be:
archive/file -< MBeans/JavaBeans
-< means many-to-one
3) I wrote SimpleSubDeployerSupport that does
archive/file -- MBean
-- means one-to-one
So my proposal is to have something like:
StandardSubDeployerSupport extends SubDeployerSupport
SimpleSubDeployerSupport extends StandardSubDeployerSupport
StandardSubDeployerSupport would allow multiple mbeans per deployment
something like
String[] getDeploymentClasses()
etc.
and SimpleSubDeployerSupport would just be a specialzation one for deployment
String[] getDeploymentClasses()
{
return new String[] { getDeploymentClass() };
}
and even that depends upon whether you think such a simplication is useful.
e.g. you may want something closer to the wire in the standard deployer?
ServiceMBean[] getMBeans()
But like I say, there isn't much point spending too much time on figuring out
an ideal abstraction when there will be a much better deployer framework in
JBoss5.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3872602#3872602
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3872602
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
