Difference between revisions of "EclipseLink/Development/JPA"

Revision as of 16:42, 16 July 2009

EclipseLink JPA 2.0 Implementation Status

The EclipseLink project has been chosen to deliver the JPA 2.0 reference implementation as part of JSR 317. This page provides a summary of the work planned and the current status.

The following are features known to be required for JPA 2.0

EDR of JPA 2.0

Feature	Status	Links	Description
MetaModel API	Assigned	bug 266912, Spec	Runtime metamodel api implementation (without the APT based canonical metamodel work in bug 267391.
Criteria API	Assigned	bug 00000, Spec	This will be an object oriented query construction api.
Validation	Assigned	bug 266927, Spec	Through this feature EclipseLink JPA will integrate with the Validation APIs. (JSR-303)
EntityManager/Query API	Assigned	bug 00000, Spec	Add support for the new EntityManager and Query APIs.
Cache Usage Settings	Assigned	bug 277039, Spec	Settings to allow fine grained control of second level cache usage.
1:1 JoinTable	Completed	bug 282553, Spec
Persistence Utils	Not Started	bug 281884, Spec	This feature covers the implementation of the new PersistenceUtils helper interfaces.
Pessimistic Locking Scope	Not Started	bug 280803, Spec	The new version of the specification provides a setting to extend pessimistic locking to certain relationships of the locked entity.
Properties Processing	Not Started	bug 000000, Spec	The new version of the specification provides a means to dynamically specify properties on the EntityManager. The goal of this feature will be to define our properties processing and validation.
Jarfile URL	Not Started	bug 281887, Spec	The specification has redefined the base for the jar-file url in the persistence.xml.
Typesafe MetaModel Generation (APT)	Not Started	bug 267391, Spec	APT based canonical metamodel generation.
JPA 1.0 Compatibility	Ongoing	Spec	Ensure that EclipseLink libraries with JPA 2.0 functionality will be able to run on JPA 1.0 compliant application servers.
Schema/Catalog on SequenceGenerator	Not Started	Spec
JoinTable override	Completed	bug 278768, Spec	JoinTable from association override support (metadata processing)
Uni-directional 1:M	Completed	bug 241414, Spec	Provide EclipseLink functionality to support a uni-directional OneToMany mapping that does not use a join table. This mapping will be similar to EclipseLink's current AggregateObjectMapping.
Access Type	Completed	bug 241651, Spec	Provide support for configurable access type
Pessimistic Locking	Completed	bug 248489, Spec	Adding support for EntityManager APIs and functionality for Pessimistic locking
Nested Embedding	Completed	bug 207823, Spec	Embedded objects can nest other embedded objects as well as being able to have relationships to entities.
Cache API	Completed	bug 248780, Spec	Add support for the new Cache APIs.
New Collection Mappings	Completed	bug 48293, bug 265359, Spec	Collections of embedded objects (aka Aggregate Collections) or of simple objects (Direct Collections)
Derived Identifiers	Completed	bug 241765, Spec	Relationship mappings can be used as Id's or components of compound Id's directly without the need for separate primitive attributes.
Extended Map Support	Completed	bug 241410, Spec	Maps can have keys and values that can be any of basic, entity, or embedded. These are stored in a target table or join table.
MappedById	Completed	bug 270011, Spec	Derived Ids that are also defined in an embeddableid mapping
Orphan Removal	Completed	bug 249033, Spec	When this option is set on a relationship if a child object is removed from the relationship it must be deleted.
TABLE_PER_CLASS Inheritance	Completed	bug 249860, Spec	Add support for TABLE_PER_CLASS inheritance strategy. Optional feature from JPA 1.0
Entity Type Expressions	Completed	bug 000000, Spec	JPA 2.0 QL has added syntax to allow restriction of query results by Entity Class type
Collection Params for IN	Completed	bug 252038, Spec	IN() in JPQL can now accept a single collection parameter.
Ordered Lists	Completed	bug 249037, Spec	Order of list is persisted to an "order column" when writes occur
Case Expressions	Completed	bug 252491, Spec	Case style expressions have been introduce to JPQL and Criteria API
Standard Properties	Completed	bug 249023, Spec	Add support for new javax.persistence properties.
JPQL Updates	Completed	bug 249224, Spec	JPA 2.0 introduces certain JPQL updates that do not correspond to other features.
Undelimited Identifiers	Completed	bug 251908, Spec	This feature covers specifying and processing metadata Identitfiers.

Bug Queries and Reports

Goals/Requirements

EclipseLink will introduce JPA 2.0 features with the following goals in mind:

Remain a compliant JPA 1.0 implementation during the development of 2.0 functionality. This is a major requirement since we are working towards a 1.0 release of EclipseLink which must be JPA 1.0 compliant.
- This generally means that the JPA 1.0 persistence.jar could be on the classpath and the product should function as expected
Conform with the Eclipse IP process and rules. This means that the use of any updated persistence libraries and their source must come into the project through proper IP review procedures.
All new features involving changes to JPA's ORM-XML schema must be reflected in Eclipse-ORM.XML. This should be done in such a way that changes during the evolution of the specification are minimized.
Where possible any new features added for JPA 2.0 should also be available to users of the native EclipseLink ORM API and metadata. Accessibility through the native API can be limited to programmatic access and configuration.
- EclipseLink users using JPA 1.0 will be able to access 2.0 preview functionality through native EclipseLink API or metadata

Types of Changes

The JPA 2.0 expert group is attempting to evolve this new specification to remain backwards compatible with JPA 1.0. The scope of its work will involve changes of various types with different effects on EclipseLink.

Metadata Changes
1. New Annotations
2. New structures in the persistence.xml XSD
3. New structures in the ORM.XML XSD
API Changes
1. New interfaces
2. New methods on existing interfaces

Development Approach

We will be developing this functionality within the main product stream. Specification defined interfaces will be created and packaged within a javax.persistence_2.0 bundle/jar for users who wish to preview the functionality. To remain backward compatible with JPA 1.0 we will be packaging any interfaces we must link with for JPA 2.0 within the eclipselink JPA bundle/jar. As this bundle/jar will not contain the EMF API users will be required to choose their JPA version by using the appropriate persistence bundle/jar. Not bundling all the interfaces allows us to produce a single EclipseLink JPA bundle/jar while alleviating the concern of user's hitting preview code when they do not expect to.

Class file to be included in EclipseLink JPA bundle

javax.persistence.Cache
javax.persistence.Access
javax.persistence.AccessType
javax.persistence.LockModeType
javax.persistence.LockTimeoutException
javax.persistence.PessimisticLockException

Metadata Changes

The following changes need to be handled keeping the backwards compatibility to JPA 1.0 goals in mind:

New Annotations
Modified Annotations
Changes to the XML Schemas
new Interfaces
reference to new interfaces

@@ Line 1: / Line 1: @@
 __NOTOC__
-== EclipseLink JPA 2.0 Implementation Status ==
+== EclipseLink JPA 2.0 Implementation Status  ==
 The EclipseLink project has been chosen to deliver the JPA 2.0 reference implementation as part of JSR 317. This page provides a summary of the work planned and the current status.
 The following are features known to be required for JPA 2.0
 [http://jcp.org/aboutJava/communityprocess/edr/jsr317/index.html EDR of JPA 2.0]
-{|{{BMTableStyle}}
+{| class="FCK__ShowTableBorders"
-|-{{BMTHStyle}}
+|-
 ! Feature
 ! Status
 ! Links
 ! Description
 |-
-| MetaModel API || Assigned || {{bug|266912}}, [[EclipseLink/Development/JPA_2.0/metamodel_api|Spec]] || Runtime metamodel api implementation (without the APT based canonical metamodel work in {{bug|267391}}.
+| MetaModel API
+| Assigned
+| {{bug|266912}}, [[EclipseLink/Development/JPA 2.0/metamodel api|Spec]]
+| Runtime metamodel api implementation (without the APT based canonical metamodel work in {{bug|267391}}.
+|-
+| Criteria API
+| Assigned
+| {{bug|00000}}, [[EclipseLink/Development/JPA 2.0/query definition api|Spec]]
+| This will be an object oriented query construction api.
+|-
+| Validation
+| Assigned
+| {{bug|266927}}, [[EclipseLink/Development/JPA 2.0/validation api integration|Spec]]
+| Through this feature EclipseLink JPA will integrate with the Validation APIs. (JSR-303)
+|-
+| EntityManager/Query API
+| Assigned
+| {{bug|00000}}, [[EclipseLink/Development/JPA 2.0/entitymanager updates|Spec]]
+| Add support for the new EntityManager and Query APIs.
 |-
-| Criteria API || Assigned || {{bug|00000}}, [[EclipseLink/Development/JPA_2.0/query_definition_api|Spec]] || This will be an object oriented query construction api.
+| Cache Usage Settings
+| Assigned
+| {{bug|277039}}, [[EclipseLink/Development/JPA 2.0/cache usaged|Spec]]
+| Settings to allow fine grained control of second level cache usage.
 |-
-| Validation || Assigned || {{bug|266927}}, [[EclipseLink/Development/JPA_2.0/validation_api_integration|Spec]] || Through this feature EclipseLink JPA will integrate with the Validation APIs. (JSR-303)
+| 1:1 JoinTable
+| Completed&nbsp;
+| {{bug|282553}}, [[EclipseLink/Development/JPA2.0/one-to-one via jointable|Spec]]
+|
 |-
-| EntityManager/Query API || Assigned || {{bug|00000}}, [[EclipseLink/Development/JPA_2.0/entitymanager_updates|Spec]] || Add support for the new EntityManager and Query APIs.
+| Persistence Utils
+| Not Started
+| {{bug|281884}}, [[EclipseLink/Development/JPA 2.0/persistence utils|Spec]]
+| This feature covers the implementation of the new PersistenceUtils helper interfaces.
 |-
-| Cache Usage Settings || Assigned|| {{bug|277039}}, [[EclipseLink/Development/JPA_2.0/cache_usaged|Spec]] || Settings to allow fine grained control of second level cache usage.
+| Pessimistic Locking Scope
+| Not Started
+| {{bug|280803}}, [[EclipseLink/Development/JPA 2.0/pessimistic lock scope|Spec]]
+| The new version of the specification provides a setting to extend pessimistic locking to certain relationships of the locked entity.
 |-
-| 1:1 JoinTable || Assigned || {{bug|282553}}, [[EclipseLink/Development/JPA2.0/one-to-one_via_jointable|Spec]] ||
+| Properties Processing
+| Not Started
+| {{bug|000000}}, [[EclipseLink/Development/JPA 2.0/properties processing|Spec]]
+| The new version of the specification provides a means to dynamically specify properties on the EntityManager. The goal of this feature will be to define our properties processing and validation.
 |-
-| Persistence Utils || Not Started || {{bug|281884}}, [[EclipseLink/Development/JPA_2.0/persistence_utils|Spec]] || This feature covers the implementation of the new PersistenceUtils helper interfaces.
+| Jarfile URL
+| Not Started
+| {{bug|281887}}, [[EclipseLink/Development/JPA 2.0/jarfile url|Spec]]
+| The specification has redefined the base for the jar-file url in the persistence.xml.
 |-
-| Pessimistic Locking Scope || Not Started || {{bug|280803}}, [[EclipseLink/Development/JPA_2.0/pessimistic_lock_scope|Spec]] || The new version of the specification provides a setting to extend pessimistic locking to certain relationships of the locked entity.
+| Typesafe MetaModel Generation (APT)
+| Not Started
+| {{bug|267391}}, [[EclipseLink/Development/JPA 2.0/metamodel api#ATP_Tooling_Library|Spec]]
+| APT based canonical metamodel generation.
 |-
-| Properties Processing || Not Started || {{bug|000000}}, [[EclipseLink/Development/JPA_2.0/properties_processing|Spec]] || The new version of the specification provides a means to dynamically specify properties on the EntityManager.  The goal of this feature will be to define our properties processing and validation.
+| JPA 1.0 Compatibility
+| Ongoing
+| [[EclipseLink/Development/JPA2.0/container support|Spec]]
+| Ensure that EclipseLink libraries with JPA 2.0 functionality will be able to run on JPA 1.0 compliant application servers.
 |-
-| Jarfile URL || Not Started || {{bug|281887}}, [[EclipseLink/Development/JPA_2.0/jarfile_url|Spec]] || The specification has redefined the base for the jar-file url in the persistence.xml.
+| Schema/Catalog on SequenceGenerator
+| Not Started
+| [[EclipseLink/Development/JPA2.0/schema-catalog-sequence-generator|Spec]]
+|
 |-
-| Typesafe MetaModel Generation (APT) || Not Started || {{bug|267391}}, [[EclipseLink/Development/JPA_2.0/metamodel_api#ATP_Tooling_Library|Spec]] || APT based canonical metamodel generation.
+| JoinTable override
-|-
+| Completed
-| JPA 1.0 Compatibility || Ongoing || [[EclipseLink/Development/JPA2.0/container_support|Spec]] || Ensure that EclipseLink libraries with JPA 2.0 functionality will be able to run on JPA 1.0 compliant application servers.
+| {{bug|278768}}, [[EclipseLink/Development/JPA2.0/association-override-join-table|Spec]]
+| JoinTable from association override support (metadata processing)
 |-
-| Schema/Catalog on SequenceGenerator || Not Started || [[EclipseLink/Development/JPA2.0/schema-catalog-sequence-generator|Spec]] ||
+| Uni-directional 1:M
+| Completed
+| {{bug|241414}}, [[EclipseLink/Development/JPA2.0/uni-directional onetomany mapping|Spec]]
+| Provide EclipseLink functionality to support a uni-directional OneToMany mapping that does not use a join table. This mapping will be similar to EclipseLink's current AggregateObjectMapping.
 |-
-| JoinTable override || Completed || {{bug|278768}}, [[EclipseLink/Development/JPA2.0/association-override-join-table|Spec]] || JoinTable from association override support (metadata processing)
+| Access Type
-|-
+| Completed
-| Uni-directional 1:M || Completed || {{bug|241414}}, [[EclipseLink/Development/JPA2.0/uni-directional_onetomany_mapping| Spec]] || Provide EclipseLink functionality to support a uni-directional OneToMany mapping that does not use a join table.  This mapping will be similar to EclipseLink's current AggregateObjectMapping.
+| {{bug|241651}}, [[EclipseLink/Development/JPA2.0/access type|Spec]]
+| Provide support for configurable access type
 |-
-| Access Type || Completed || {{bug|241651}}, [[EclipseLink/Development/JPA2.0/access_type|Spec]] || Provide support for configurable access type
+| Pessimistic Locking
+| Completed
+| {{bug|248489}}, [[EclipseLink/Development/JPA 2.0/pessimistic locking|Spec]]
+| Adding support for EntityManager APIs and functionality for Pessimistic locking
 |-
-| Pessimistic Locking || Completed || {{bug|248489}}, [[EclipseLink/Development/JPA_2.0/pessimistic_locking|Spec]] || Adding support for EntityManager APIs and functionality for Pessimistic locking
+| Nested Embedding
+| Completed
+| {{bug|207823}}, [[EclipseLink/Development/JPA 2.0/nested embedding|Spec]]
+| Embedded objects can nest other embedded objects as well as being able to have relationships to entities.
 |-
-| Nested Embedding || Completed || {{bug|207823}}, [[EclipseLink/Development/JPA_2.0/nested_embedding|Spec]] || Embedded objects can nest other embedded objects as well as being able to have relationships to entities.
+| Cache API
+| Completed
+| {{bug|248780}}, [[EclipseLink/Development/JPA 2.0/cache api|Spec]]
+| Add support for the new Cache APIs.
 |-
-| Cache API || Completed || {{bug|248780}}, [[EclipseLink/Development/JPA_2.0/cache_api|Spec]] || Add support for the new Cache APIs.
+| New Collection Mappings
+| Completed
+| {{bug|48293}}, {{bug|265359}}, [[EclipseLink/Development/JPA 2.0/new collection mappings|Spec]]
+| Collections of embedded objects (aka Aggregate Collections) or of simple objects (Direct Collections)
 |-
-| New Collection Mappings || Completed || {{bug|48293}}, {{bug|265359}}, [[EclipseLink/Development/JPA_2.0/new_collection_mappings|Spec]] || Collections of embedded objects (aka Aggregate Collections) or of simple objects (Direct Collections)
+| Derived Identifiers
+| Completed
+| {{bug|241765}}, [[EclipseLink/Development/JPA2.0/derived ids|Spec]]
+| Relationship mappings can be used as Id's or components of compound Id's directly without the need for separate primitive attributes.
 |-
-| Derived Identifiers || Completed || {{bug|241765}}, [[EclipseLink/Development/JPA2.0/derived_ids|Spec]] || Relationship mappings can be used as Id's or components of compound Id's directly without the need for separate primitive attributes.
+| Extended Map Support
+| Completed
+| {{bug|241410}}, [[EclipseLink/Development/JPA2.0/Extended Map support|Spec]]
+| Maps can have keys and values that can be any of basic, entity, or embedded. These are stored in a target table or join table.
 |-
-| Extended Map Support || Completed || {{bug|241410}}, [[EclipseLink/Development/JPA2.0/Extended_Map_support|Spec]] || Maps can have keys and values that can be any of basic, entity, or embedded. These are stored in a target table or join table.
+| MappedById
+| Completed
+| {{bug|270011}}, [[EclipseLink/Development/JPA 2.0/mappedbyid|Spec]]
+| Derived Ids that are also defined in an embeddableid mapping
 |-
-| MappedById || Completed || {{bug|270011}}, [[EclipseLink/Development/JPA_2.0/mappedbyid|Spec]] || Derived Ids that are also defined in an embeddableid mapping
+| Orphan Removal
+| Completed
+| {{bug|249033}}, [[EclipseLink/Development/JPA 2.0/orphan removal|Spec]]
+| When this option is set on a relationship if a child object is removed from the relationship it must be deleted.
 |-
-| Orphan Removal || Completed || {{bug|249033}}, [[EclipseLink/Development/JPA_2.0/orphan_removal|Spec]] || When this option is set on a relationship if a child object is removed from the relationship it must be deleted.
+| TABLE_PER_CLASS Inheritance
+| Completed
+| {{bug|249860}}, [[EclipseLink/Development/JPA 1.0/table per class|Spec]]
+| Add support for TABLE_PER_CLASS inheritance strategy. Optional feature from JPA 1.0
 |-
-| TABLE_PER_CLASS Inheritance || Completed || {{bug|249860}}, [[EclipseLink/Development/JPA_1.0/table_per_class|Spec]] || Add support for TABLE_PER_CLASS inheritance strategy. Optional feature from JPA 1.0
+| Entity Type Expressions
-|-
+| Completed
-| Entity Type Expressions || Completed || {{bug|000000}}, [[EclipseLink/Development/JPA_2.0/entity_type_expressions|Spec]] || JPA 2.0 QL has added syntax to allow restriction of query results by Entity Class type
+| {{bug|000000}}, [[EclipseLink/Development/JPA 2.0/entity type expressions|Spec]]
+| JPA 2.0 QL has added syntax to allow restriction of query results by Entity Class type
 |-
-| Collection Params for IN || Completed  || {{bug|252038}}, [[EclipseLink/Development/JPA_2.0/collection_parameters_for_in|Spec]] || IN() in JPQL can now accept a single collection parameter.
+| Collection Params for IN
+| Completed
+| {{bug|252038}}, [[EclipseLink/Development/JPA 2.0/collection parameters for in|Spec]]
+| IN() in JPQL can now accept a single collection parameter.
 |-
-| Ordered Lists || Completed || {{bug|249037}}, [[EclipseLink/Development/JPA_2.0/ordered_lists|Spec]] || Order of list is persisted to an "order column" when writes occur
+| Ordered Lists
+| Completed
+| {{bug|249037}}, [[EclipseLink/Development/JPA 2.0/ordered lists|Spec]]
+| Order of list is persisted to an "order column" when writes occur
 |-
-| Case Expressions || Completed || {{bug|252491}}, [[EclipseLink/Development/JPA_2.0/case_expressions|Spec]] || Case style expressions have been introduce to JPQL and Criteria API
+| Case Expressions
+| Completed
+| {{bug|252491}}, [[EclipseLink/Development/JPA 2.0/case expressions|Spec]]
+| Case style expressions have been introduce to JPQL and Criteria API
 |-
-| Standard Properties || Completed || {{bug|249023}}, [[EclipseLink/Development/JPA_2.0/standard_properties|Spec]] || Add support for new javax.persistence properties.
+| Standard Properties
+| Completed
+| {{bug|249023}}, [[EclipseLink/Development/JPA 2.0/standard properties|Spec]]
+| Add support for new javax.persistence properties.
 |-
-| JPQL Updates || Completed || {{bug|249224}}, [[EclipseLink/Development/JPA_2.0/jpql|Spec]] || JPA 2.0 introduces certain JPQL updates that do not correspond to other features.
+| JPQL Updates
+| Completed
+| {{bug|249224}}, [[EclipseLink/Development/JPA 2.0/jpql|Spec]]
+| JPA 2.0 introduces certain JPQL updates that do not correspond to other features.
 |-
-| Undelimited Identifiers || Completed || {{bug|251908}}, [[EclipseLink/Development/JPA_2.0/undelimited_identifiers|Spec]] || This feature covers specifying and processing metadata Identitfiers.
+| Undelimited Identifiers
+| Completed
+| {{bug|251908}}, [[EclipseLink/Development/JPA 2.0/undelimited identifiers|Spec]]
+| This feature covers specifying and processing metadata Identitfiers.
 |}
-=== Bug Queries and Reports ===
+=== Bug Queries and Reports  ===
-* [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=substring&short_desc=JPA+2.0&classification=RT&product=EclipseLink&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= All Open Bugs with 'JPA 2.0' in summary]
+*[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=substring&short_desc=JPA+2.0&classification=RT&product=EclipseLink&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= All Open Bugs with 'JPA 2.0' in summary]
-* [https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_status&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=substring&short_desc=JPA+2.0&classification=RT&product=EclipseLink&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bug Report]
+*[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_status&y_axis_field=assigned_to&z_axis_field=&query_format=report-table&short_desc_type=substring&short_desc=JPA+2.0&classification=RT&product=EclipseLink&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bug Report]
-* [https://bugs.eclipse.org/bugs/report.cgi?y_axis_field=&cumulate=0&z_axis_field=&format=bar&x_axis_field=bug_status&query_format=report-graph&short_desc_type=substring&short_desc=JPA+2.0&classification=RT&product=EclipseLink&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=LATER&resolution=REMIND&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED&resolution=NOT_ECLIPSE&resolution=---&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Graph]
+*[https://bugs.eclipse.org/bugs/report.cgi?y_axis_field=&cumulate=0&z_axis_field=&format=bar&x_axis_field=bug_status&query_format=report-graph&short_desc_type=substring&short_desc=JPA+2.0&classification=RT&product=EclipseLink&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=LATER&resolution=REMIND&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED&resolution=NOT_ECLIPSE&resolution=---&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Graph]
 == Goals/Requirements ==

Breadcrumbs

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.