Community
Participate
Working Groups
The JPA Diagram Editor should support JPA 2.0 entities to match the existing support for JPA in currently in Eclipse. JPA 2.0 is the default JPA version for new JPA projects in WTP.
(In reply to comment #0) > The JPA Diagram Editor should support JPA 2.0 entities to match the existing > support for JPA in currently in Eclipse. JPA 2.0 is the default JPA version > for new JPA projects in WTP. Of course. It's in our plan. For now we just enabled the editor for JPA 2.0 projects, but I hope that before the end of March 2011 we'll have full JPA 2.0 support. We also have internal stake-holders which require it. So, don't worry - we didn't forget :) 10x for opening the bug.
Neil, the JPA 2.0 use case is new to our team and we are currently educating ourselves on the topic. It will be very helpful if you can open bugs for what is missing and give references and examples, so we can be quickly introduced with the new features of the spec.
I think the following new JPA 2.0 concepts would be the main areas to look at for the Diagram Editor. - Uni-directional One to Many[1] - ElementCollection mapping[2] - Derived Id[3] [1] - http://wiki.eclipse.org/EclipseLink/Development/JPA2.0/uni-directional_onetomany_mapping [2] - http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/new_collection_mappings [3] - http://wiki.eclipse.org/EclipseLink/Development/JPA2.0/derived_ids Also see the spec: http://www.jcp.org/en/jsr/detail?id=317
The 3.2 target now represents the Juno release.
Retargeting to the Kepler realease (3.3).
Since the three major features of JPA 2.0 specification have been already implemented, the dialog, which appeared by opening a JPA 2.0 project's diagram editor, saying that there is only a partial support for JPA 2.0 spec, must be removed.
No feature exception needed for this one. Very minor.
The warning dialog is removed with the following git commit: https://git.eclipse.org/c/dali/webtools.dali.git/commit/?id=d175cc17569ea3d92458d6ef370ededd52f50743