With the old style of JBoss Deployers, a single deployer implementation would handle all the processing for the matching top level deployment unit. This behaviour was completely changed in the new Deployers architecture. Here we have a new way of handling deployment unit, we call it an aspectized deployment, meaning that each deployer implementation does just one thing. This way it is easier to control how much it gets done and even easier to swap out the behaviour. But what is that one thing? We are all familiar with parsing, creating ClassLoaders, installing services, etc. So, basically any part of previous deployment process, we can see as a separate process, parsing the jboss-service.xml file, creating ServiceMetaData, setting up RepositoryCL and finally registring MBeans into the MBeanServer instance.

Let's see this aspectization on the listing below. This is a real example from the current Microcontainer beans deployment.