Bug 330107

Summary:	Add support for JPA 2.0 Entities
Product:	[WebTools] Dali JPA Tools	Reporter:	Neil Hauge <neil.hauge>
Component:	Diagram Editor	Assignee:	Project Inbox <dali.diagrameditor-inbox>
Status:	RESOLVED FIXED	QA Contact:	Stefan Dimov <stefan.dimov>
Severity:	enhancement
Priority:	P3	CC:	kaloyan, petya.sabeva
Version:	unspecified	Keywords:	plan
Target Milestone:	3.3 M7	Flags:	neil.hauge: review+
Hardware:	PC
OS:	Windows 7
Whiteboard:
Bug Depends on:	338395, 364597, 364603
Bug Blocks:

Description Neil Hauge

2010-11-12 11:30:46 EST

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.

Comment 1 Stefan Dimov

2010-11-15 07:45:17 EST

(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.

Comment 2 Kaloyan Raev

2010-11-16 02:37:25 EST

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.

Comment 3 Neil Hauge

2010-12-02 18:04:08 EST

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

Comment 4 Neil Hauge

2011-10-27 11:16:45 EDT

The 3.2 target now represents the Juno release.

Comment 5 Petya Sabeva

2012-05-04 01:53:05 EDT

Retargeting to the Kepler realease (3.3).

Comment 6 Petya Sabeva

2013-03-15 08:46:27 EDT

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.

Comment 7 Neil Hauge

2013-03-15 09:54:51 EDT

No feature exception needed for this one.  Very minor.

Comment 8 Petya Sabeva

2013-04-10 11:12:56 EDT

The warning dialog is removed with the following git commit:

https://git.eclipse.org/c/dali/webtools.dali.git/commit/?id=d175cc17569ea3d92458d6ef370ededd52f50743