Community
Participate
Working Groups
One of our users noted that if you add the JPA facet to a project it adds the persistence.xml and orm.xml files at that time. But if you later remove the JPA facet, those resources are left around. I'm not sure what the general behavior for most facets is in the similar circumstance. It might make sense that the artifacts should be cleaned up when the facet is removed. I guess it depends on what the user would intend by removing the facet - if they no longer wanted JPA support in the application and removed the facet, when they ran on the server all of the JPA artifacts would still be loaded/executed which might no longer be intended.
Yes, this was intended behavior. We didn't feel comfortable *deleting* resources when the facet was removed, especially because some users prefer to keep editing their JPA resources without our facet present. Marking this as an enhancement.
I think in order to implement this there would need to be an additional step on Facet removal that allowed for a decision to be made by the user. I'm not sure if there is any support for this in the facet framework at this time, but it is something that could be looked into.
Moving JPA specific bugs to new JPA component in bugzilla.
