"scott.stark(a)jboss.org" wrote : Maybe this could be a list/set of resolvers in the AbstractBootstrapProfileFactory so that its recursive logic still could be used to resolve both the profile and subprofiles across all of the resolvers. I'll work on this approach a bit. Hmm okay - but there is also a ProfileFactory, so the resolver should either just resolve the ProfileMetaData or use the ProfileFactory then - whereas there could also be more ProfileFactories, one for each profile meta data type. Furthermore the AbstractBootstrapProfileFactory should actually do more than it's doing now. There are some weird implicit dependencies set, to ensure the correct ordering during the bootstrap. We might want to change this behavior, that the AbstractBootstrapProfileFactory also registers and activates the Profiles based on the ordering in the xml and just keep explicit dependencies. Therefore we might want to remove the automatic validation of Profiles in the ProfileService and let the caller decide when to validate. So i'll do something else in the meantime and let you work on that a bit. I can continue later and finish the remaining stuff on my todo list. This is also good so that you can check if you actually like my changes :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206457#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...