New Deployer changes - overview
adrian.brock Jun 28, 2007 9:25 AMThis is a quick brain dump of all the deployer changes I just committed.
As usual this is an overview thread, to collect all the information in one place.
Create separate threads if you want to discuss indivdual topics in more detail.
First, the changes are not yet complete.
1) AOP - AOP has a deployer inside its project. That needs updating
and AOP re-releasing. But since AOP is required for EJB3
I've temporarily hacked a new version in the "system" project in
org.jboss.aop.temp.AOPDeployer
2) WS - Similarly webservices have their own deployers.
I've just disabled webservices for now. I'll be working on this next
once I've looked at some other minor loose ends.
3) EJB3 - I've updated the EJB3 deployers to use attachment flows (see below)
but I'm not sure if they are correct. Its working on some
of the basic tests in the ejb3 project tests.
I suspect there may need to be some attachment flow dependency on the
security deployer (possibly others?), but I'm not sure where it needs to go.
4) Security - I think this needs a lot more work to where I would like to get it.
5) Embedded - I haven't updated this project to the new deployers.
The version I currently have of this project doesn't build so that needs to be fixed
before I can do this. Most of the changes should be minor, i.e. updating
it to use the new "client side" deployment api.
I'm going to break down these posts into the follow areas:
* New Project Structure - separation of spi/impl and vfs, etc.
* VFSDeployer - why this extra abstraction is important
* Core - a quick discussion on the core project
* Client - the new "client side" deployment api
* Structure - the changes to the structure deployments and how the structure is built
* MainDeployer - the changes to the main deployer and how it relates to the client side api
* DeploymentContext - how that is nearly invisible now and what needs to be done to complete the process
* Deployers - the new stages (real dependencies), attachment flow, changes to how components work, making the parsing deployers "more declarative"
* TODO - other work that still needs doing like integrating the new classloader