"adrian(a)jboss.org" wrote : | If you look in broad brush terms, the profile service is made up of two components | | 1) A client side api that lets you define what a profile is | 2) A server side that implements that profile at runtime | | For the current default profile (hot deployment) that means three pojos that know how | to scan three sets of directories/urls (bootstrap/deployers/deploy) | which are the three sub-profiles that make up the profile. | The client side api for the default hot deployment profile is of course to just modify the directory structure and the file contents. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154475#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...