So starting to get tired - so just a brief update: I committed my current changes to profileService and of course broke your prototype already :) As the AbstractProfileFactory was just a way to test xml testing and providing a config which behaves similar to the current implementation. I will look into providing a ProfileFactory which actually does what you expected - for now i just added a hack to make it compile again... The main part which changes is basically to the xml format and i've put a simple example in the AS testsuite. You can create the configuration by running: [testsuite]$ ./build.sh embedded-config When you then start this configuration it looks into conf/profiles and starts AS based on this configuration. In this case it will boot a web-profile. (Although it seems there are quite a lot requirements to deploy a static index.html :) As mentioned before i'm not really happy with the implicit dependencies (a sub-profile is just a reference to a different profile) which are set when creating the bootstrap profiles, as it always adds a reference to the previous profile. Maybe we also want to add a specific root.profile.xml - like bootstrap.xml. Where you skip setting implicit dependencies and just activate them based on the ordering (i guess that would be the best way) There are some other thoughts/issues i would like to mention e.g. dropping VFSDeployment from the spi This for example also has an affect to the AbstractProfile - as i think most things which the DeploymentRepository does should be done by the profile itself - or somewhere else But i think i'll post about that later :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204482#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...