Community
Participate
Working Groups
In the JPA Details view for a relationship mapping we currently have a link for the target-entity which takes you to the java editor. We need a way for the user to get to the orm.xml/eclipselink-orm.xml file if that is where the mapping information is defined or overriden. Need to allow the user to pick or we could also make a guess and take them to the option that wins in overrides.
Along these sames lines we could have a way to go to the corresponding relationship mapping for a bi-directional mapping. The ability to do this from within the java/xml editors would be nice as well, though I'm not sure yet how that would work.
Moving JPA specific bugs to new JPA component in bugzilla.
This is potentially more important when we have dynamic persistence support where there is no java. Currently the Target Entity link will open the new class wizard. It should instead jump to the entity where it is defined elsewhere in the orm.xml file or in another orm.xml file.
Created attachment 220359 [details] proposed patch The patch works as the following: - if the target entity is OrmPersistentType, open the mapping file containing the persistent type and then set the selection focus to that persistent type - if the target entity is not OrmPersistentType, check if its corresponding Java type exists, if yes, open the Java type; otherwise, open the create new class wizard Cases with validation errors, such as duplicates persistent types, are not handled with this patch thinking that's users' responsibility to fix the validation errors to get exactly what they want. There is a comment related to this in the patch. You can remove it if you think we don't need it.
Patch committed.
