The path elements as config parts of e.g. a standalone server have entries that are computed by the server and are in fact read/only. They have the "read-only" checkbox set. See also Bug 817540 Due to limitations in the UI, they are still shown as editable and deletable, but in fact both will not work. If the user deletes them and stores the config, they will re-appear. Path that are r/o start with java. jboss. user. The read-only checkbox is "write-once" meaning that if a user adds a new path entry and sets this checkbox to true or false, it will stick and become immutable. To change it, the path entry needs to be deleted and re-added
Situation is different (unfortunately): If the user tries to delete an entry that has the read-only checkbox checked, we have no way of finding this out(*) and pass the removal to as7 which then throws an error. This means, the user must not try to edit or remove those entries. *) We can not prevent removal at all, at the user may try to remove one of the entries he has added previously and this is allowed. See also Bug 818549 and Bug 818546
per BZ triage crouch, foley, loleary
Should be covered here: http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/3.1/html/How_to_Manage_JBoss_Servers/system-paths.html
Bulk closing of BZs that have no target version set, but which are ON_QA for more than a year and thus are in production for a long time.