We should separate user applications from JBoss system functionality; currently we encourage people to dump user apps in deploy folder.

Doing the following provides clean separation and allows users to apply different security rights to these folders (ex. sys admins access system and app admins access deploy)

We should:
1. Create a system folder that is a sibling of deploy and place JBoss components to deploy in this folder

2. We should keep the current deploy folder so that users can continue to use it for their deployed apps; we may consider calling this folder apps instead to be more explicit

3. We should update the corresponding jboss-service.xml to scan both these folders

A somewhat related idea worth considering with the above includes:

• What about extending the binding manager and being able to not only override jmx attributes but also shut-off/disable services? Hence, without having to worry about the content of deploy, people could keep their override-binding.xml file for all versions of JBoss and this would disable services and reconfigure the ones they want to customize (ip port, etc.)?