deployer prototype
bill.burke Apr 27, 2006 10:11 PMI recently checked in a Deployer prototype within the kernel/ module under the org.jboss.deployment package. There is also a TestCase under tests/org/jboss/test/deployment.
It is mostly bare bones with code taken from the Embeddable EJB3 deployment. THe goal of the prototype was to have a generic deployment mechanism that is usable in a Java SE environment, but with some thought put into how it can morph into a full-blown application server environment with scoped classloading.
What I got so far is a MainDeployer, Deployment, Deployer, and DeployerAspect interfaces. It has the notion of DeployerAspects at the MainDeployer configured level. There is one classloader deployer aspect, but all it does is sets the Deployment's classloader to be the TCL. Right now, if you look at the testsuite. It has one example that scans a jar and directory based classpath for MC -beans.xml files to deploy. It has one MCDeployer implemented.
Unless I get shutdown by you guys, my next steps are:
1. Get embeddable EJB3 stack running in this environment: AOP deployer and EJB3 Deployer.
2. Write an "app server" version that incorporates Scott's VFS classloader. Figure out how deployer aspects can be used for this. If the AOP/MC integration is done, I think interception should be done/configured per deployer rather than at the MainDeployer level. I'll fiddle with this to see what can be done and what works.
3. Define a usecase for the profiler (i.e. MDB configuration options). Pull in parts of the Scott's profiler service APIs and fool around with how these options could be saved/exposed/etc.. at runtime. I would play with any APIs Scott/Adrian come up with, pulling, copying, pasting, reusing profile service code. The deal would be to evolve something that already works in steps 1 and 2.
I can probably have all three done by JBoss World if you can wait that long. Would have it done sooner but, I have training and Java One coming up as well as another EJB3 release.
Bill