Related to several discussions about how the profile service should be part of the bootstrap process, supporting embedded:
ProfileService API
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=146270
Towards a canonical server:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=142477
Today's call on how the services that should be included in a unit test that relies on embedded are defined, I want to discuss how embedded and the profile service relate.
Right now the bootstrap of AS itself is outside of the profile service:
http://www.jboss.org/community/docs/DOC-10522
Right now I don't think any of the beans loaded during the bootstrap phase before the profile service is loaded affect JavaEE behaviors, so what deployers and beans could still fall under the ProfileServiceBootstrap. Getting the repository spi fleshed out sufficiently to allow for to include the test services from either annotation, xml, or a combination of these along with basic criteria is where we need to get to.
Another related issue on how managed components like system properties affect launch and bootstrap:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4194697