Description of problem:
When using the ProfileService API, one can create a queue, topic, datasource (or possibly any other config file backed "entity"), which will create a corresponding XML configuration file in the deployment directory automatically (queue_XXX-service.xml, XXX-ds.xml, etc.).
When such entity is deleted (again through the ProfileService API), the configuration file is NOT deleted but the change is merely recorded in the data/attachments "journal".
An attempt to re-create such previously deleted entity fails with a complaint that "java.io.SyncFailedException:Deployment content already exists: /.../jboss-eap-5.2.0/jboss-as/server/default/deploy/testDS-ds.xml"
Version-Release number of selected component (if applicable):
discovered using EAP 5.2.0
Steps to Reproduce:
See the dependent JBoss ON BZ on how to reproduce this using JBoss ON.
The re-creation of the entity fails complaining about an existing deployment file.
The re-creation of the entity should be successful regardless of a presence of a certain (ineffective) config file in the deploy dir.
I spoke too soon, ignore this.
The config files are considered deployments, while the individual entities in them are considered components. Removing a component doesn't remove the deployment. JBoss ON should be more clever about this and remove "empty" deployments.