Community
Participate
Working Groups
1. Create a JPA entity (and to synchronize with classes in persistence.xml during creation). 2. From Project Explorer, right-click on the entity and select refactor/move. Select a new package. 3. Upon completion, you'll see errors in the Problems view: "Class "com.ENTITYNAME" cannot be resolved" in persistence.xml The location of the classes in persistence.xml were not updated during refactoring. It would be nice if Dali could hook into the JDT refactoring framework - since the persistence.xml is already modeled, it should be pretty easy to update during refactoring.
I agree that this would be a nice feature enhancement. In this case, a nice workaround is to Synchronize Classes on the persistence.xml after refactoring, and this would update the class reference.
*** Bug 250795 has been marked as a duplicate of this bug. ***
Ran out of time for this in 2.2.
It appears you are already participating in the move refactor as the packages are updated. It doesn't seem like it would be that difficult to participate in the delete refactor.
That would be part of the JDT refactoring as Dali does not yet participate in any refactoring operations. We have wanted to add this functionality for a long time. Targeting for the next release.
Dali needs to participate in the refactoring of java types by updating the persistence.xml and mapping files. This bug will cover updating the persistence.xml and mapping files during the following refactorings: Delete/Rename/Move Java class Delete/Rename/Move Java package Delete/Rename/Move Java source folder See the wiki design doc: http://wiki.eclipse.org/Dali_Project/FeatureDocs/DaliRefactoringParticipants
*** Bug 272188 has been marked as a duplicate of this bug. ***
fixed in M1