"adrian(a)jboss.org" wrote : | If that is the case then you also could say (regardless of clustering) that a hot deployment scanner could be added to any profile service implementation. | | Again this orthogonal. | | It's then a hybrid profile service implementation. Where some sub-profiles | come from a versioned repository and others are unversioned in a directory. | Right, but there is a notion of "modified deployments" in the profile spi, and the hot deployment scanner implementation uses this. If we add a APPLICATION_TRANSIENT notion, whether the profile should detect modifications needs to be defined. Currently the profile implementations only look at the APPLICATION phase deployments. "adrian(a)jboss.org" wrote : | Whichever way you look at it, its still a sub-profile of the profile in operation | and needs some "metadata" to say how/if/when it gets activated. | | Ideally this should be a part of the management console where somebody can say this sub-profile/deployment gets activated according to this policy, | where the policy is a part of the profile itself. | Ok, I'll have to look at how deployment level policies (sub-profiles) could be implemented consistently regardless of the profile service implementation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155735#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...