Summary: | Removing JPA facet does not clean up resources | ||
---|---|---|---|
Product: | [WebTools] Dali JPA Tools | Reporter: | Tom Mutdosch <mutdosch> |
Component: | JPA | Assignee: | Neil Hauge <neil.hauge> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | neil.hauge, paul.fullbright |
Version: | 1.0.1 | Keywords: | helpwanted |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Tom Mutdosch
2007-11-19 18:13:40 EST
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. |