anonymous wrote : I know that 1) can be done easily enough. Trouble is that it makes Seam more difficult to learn and to support. Really, how so? Package format would remain the same as it currently is, except bootstrap and config of bootstrap is the same as embedded jboss, jboss. Again, the end goal being that all our projects/products are configured, deployed, bootstrapped and installed the same way or as similar as possible. anonymous wrote : Regarding hotdeploy, I may be wrong I don't see how that can ever work for the *individual Seam components*. However, larger units such as EJB jars and WARs should support hotdeploy, but that does not really require changes to Seam. I highly doubt there won't be configuration requirements... I looked at your code and what you're doing deployment wise is *exactly* the same as what the kernel does except it is solely specific to Seam, minus the flexility. MC/kernel gives an abstraction for deployment so that things like management can be snapped on later. Deployment has changed radically in JBoss 5. In the old kernel, there was a one to one relationship between deployer and archive. In JBoss 5 kernel, each deployer has a chance to look at and process each archive. Some of the things Scott is architecting into the ProfileService will allow deployers to serialize/most of their metadata so that the next time the app server is booted up (or the WAR redeployed) deployment is a lot faster as you can skip the metadata phase and just focus on binding. Not only that, but a lot of thought has been put into how things could be configured through IDEs and such. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009002#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...