I have completely rethought basic idea about the implementation of this test. Although I had consulted the issue with both Dominik and Jiri, I thought I was testing a nonsense. Maybe it will be better to reformulate the issue, because it is very brief. I think the issue is about testing of bootstrap dependencies between services already in the profile. Therefore, for example the EJB3 test should contain a SAR using some EJB3 beans (stateless, stateful) with an appropriate dependency to Ejb3Container wrote in its jboss-service.xml. The snippet of the EJB3's SAR code: public class BootstrapDependencyEJB3Test | extends ServiceMBeanSupport | implements BootstrapDependencyEJB3TestMBean | { | ... | | @EJB | DummyStatelessLocal stateless; | | @Override | protected void startService() throws Exception | { | log.debug("BootstrapDependencyTest's SAR is starting"); | | stateless.testCall(); // do nothing special | | log.debug("BootstrapDependencyTest's SAR is started"); | } | ... | } The SAR's jboss-service.xml: <?xml version="1.0" encoding="UTF-8"?> | <deployment xmlns="urn:jboss:bean-deployer:2.0"> | <bean name="BootstrapDependencyEJB3Test" class="org.jboss.test.deployers_jbas5349.sar.BootstrapDependencyEJB3Test"> | <depends>Ejb3Deployer</depends> | </bean> | </deployment> After start of the JBoss server the testcase tests just if the SAR was started. Of course, the name of the SAR will be something like Aaa-bootstrap-dependency-jbas5349-ejb3.sar. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178062#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...