&quot;bstansberry(a)jboss.com&quot; wrote : | Didn't work -- the deploy-hasingleton.profile wasn't registered. ProfileServiceBootstrap only registers the 'embedded' profile and its subprofiles. Independent ones are not registered. | Yes this is a limitation of the current implementation/example. The original idea was to have something like: common/profiles/ and conf/profiles - where you could then basically say that all profiles in conf/profiles are getting registered. And only the root.profile gets activated (not really sure about that yet) &quot;bstansberry(a)jboss.com&quot; wrote : | OT, I'm starting to think about how to use an independent profile to do farming. A farmed profile would use a different DeploymentRepository impl. | independent profile is correct, although i'm not really happy with the DeploymentRepository stuff. if you e.g. look at the FilteredDeploymentRepositoryFactory - where the repository is doing the filtering. IMHO this should actually be done by the Profile itself. Maybe the xml also needs some updating - as currently the profile is more or less defined over it's profile-source. You can basically plugin this process by creating your own ProfileSourceMetaData. You then would need to register this metadata over the singletonSchemaFactory (or whatever this is called) with it's own namespace and your own DeploymentRepositoryFactory, which gets called based on the type of the source metadata. Although this would need to be registered in the bootstrap/profile-service.xml That's how it's basically looks at the moment: | <profiles | xmlns="urn:jboss:profileservice:profiles:1.0" | name="profiles"> | <profile name="immutable"> | <profile-source> | <source>${jboss.server.home.url}conf</source> | </profile-source> | <sub-profile>ejb3</sub-profile> | <deployment>myEjb3Deployment.ear</deployment> | </profile> | <profile name="mutable-source"> | <hotdeployment-source> | <source>${jboss.server.home.url}deploy</source> | </hotdeployment-source> | <sub-profile>immutable</sub-profile> | </profile> | <profile name="maven-source"> | <maven-source xmlns="urn:jboss:profileservice:source:maven:1.0"> | <source>http://repository.jboss.org/maven2</source> | </maven-source> | <sub-profile>hotdeployment</sub-profile> | <deployment>org/jboss/jboss-profileservice/6.0.0-GA/profileservice-spi.jar</deployment> | </profile> | </profiles> | But as said maybe profiles should be defined as <hot-deployment-profile/> <maven-profile/> <ha-singleton-profile/> or something like that ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204972#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...