OpenJPA Logo   ASF Logo

OpenJPA 2.1 Tasks

Under Construction... This is just an initial cut... We will need these tasks further broken down into manageable two week iteration chunks of work... And, I have probably forgotten some new features or minor update... We will also need to create corresponding JIRAs to get the code integrated...

But, this will give us an idea of the amount of work ahead of us...

General (Preliminary) Tasks

Status JIRA Summary
Done Not Needed Need to cut an OpenJPA 2.3.0 release and associated service stream
Not Started OPENJPA-???? Upgrade to JPA 2.1 interfaces in trunk
Not Started OPENJPA-???? Evaluate Pinaki's 2.1 sandbox and merge with trunk (post 2.3.0 release)
Done OPENJPA-2459 Upgrade trunk to Java 7 for build and test
Not Started OPENJPA-???? Prep for JPA 2.1 TCK (Existing JPA 2.0 TCK instructions)

JPA 2.1 Spec Features

Status JIRA(s) Effort Summary Area JPA 2.1 Spec Reference(s)
Not Started OPENJPA-???? High Add ON condition to JPQL query.

Will require BNF change (see jpql.jjt). Can ripple across the codebase.
JPQL 4.4.5.2, 4.14
Not Started OPENJPA-???? High Downcast relation paths with TREAT operator in JPQL queries. Will require BNF change. The BNF changes will be non-trivial as TREAT can appear as a path component e.g. p.TREAT(p.items as Book).pageCount.

JPQLEpressionBuilder will require change to process the treated path. The downstream changes on building the appropriate expression will not be a heavy task as the current kernel expressions support the notion of implicit types.
JPQL 4.4, 4.4.4.1, 4.4.5, 4.4.9, 4.6.16, 4.14
Not Started OPENJPA-???? Low Use database function or user-defined function with FUNCTION operator in JPQL queries The support for this feature exists. The task is mainly to parse (JPQLEpressionBuilder) and connect to the appropriate kernel expression. JPQL 4.6.17.3, 4.14
Not Started OPENJPA-???? Low Object construction in mapping results from native SQL query The support for this feature exists in ResultShape object. Query 3.10.16.2.2, 3.10.16.3, 12.3
Not Started OPENJPA-???? Medium Add ON condition to Criteria Query The on() function is to be added to each derivation of Join separately because of generic signature of the method. Criteria 4.4.5.2, 6.3.17, 6.3.20, 6.3.21, 6.3.22, 6.3.23, 6.5.3
Not Started OPENJPA-???? Medium Add TREAT operator in Criteria query Each derivation of Path interface will require a downcast construct e.g. a class like PathImpl$Treated because the return type of the classes that implement path has generic type signature in OpenJPA implementation. A downcast (or treated) path must have a different generic signature for compile-time type checking. Criteria 6.3.1, 6.5.7
Not Started OPENJPA-???? Medium Delete via Criteria query. The design challenge for this task is to reuse the existing code for query portion of existing implementation. Criteria 6.3.1, 6.3.6, 6.5.15
Not Started OPENJPA-???? Medium Update via Criteria query. Same comment as the above task. The good news is that the refactoring has been done. Criteria 6.3.1, 6.3.5, 6.5.15
Not Started OPENJPA-???? Very High Invoke Stored Procedure. The basic support for CallableStatement exists in OpenJPA. However, this feature is going to impact several aspects of current query execution model. A stored procedure can result into multiple types of result sets while the current execution model assumes that a query returns a single type of result. It is unclear at this point how best to handle such multiplicity. Also parameter processing (always a rather weak/heuristic aspect of OpenJPA) requires extension. Query 3.1.1, 3.10.17, 10.4.3, 10.4.4, 12.2, 12.2.2.9, 12.2.3.20, 12.3
Not Started OPENJPA-???? Low Bulk update of the members of an embeddable collection. Query 3.10.16.1
Not Started OPENJPA-???? Medium Context Dependency Injection via Entity Listeners Listeners 3.5.1, 9.1
Not Started OPENJPA-???? Medium Create EntityManager with SynchronizationType.UNSYNCHRONIZED. Unsynchorized context requires to be explicitly joined to a JTA transaction, as opposed to SYNCHRONIZED contexts that are automatically joined to a JTA transaction if available.

If an unsynchronized context is not joined to a transaction, queries with pessimistic locks, bulk update or delete queries will throw the TransactionRequiredException.

The context propgation rules differ and certain restrictions apply when the context is unsynchronized.

A new method of EntityManager affirms if a context has joined a transaction.

It is recommended that a non-JTA datasource be specified for use by the persistence provider for a persistence context of type SynchronizationType.UNSYNCHRONIZED that has not been joined to a JTA transaction in order to alleviate the risk of integrating uncommitted changes into the persistence context in the event that the transaction is later rolled back.

Container implications as well...
Transactions 3.3, 3.3.1, 7.2.1, 7.4, 7.6.1, 7.6.2, 7.6.3, 7.6.4.1
Not Started OPENJPA-???? High Type conversion of basic attributes. The basic support for conversion exists as Externalizer. But the new conversion facility covers a wider type of properties that can be externalized. Also specification to convert the data type can be attached to the class definition. Such a feature is not available in OpenJPA. EM 3.8
Not Started OPENJPA-???? Medium Conversion facility.

Parsing @Converter annotation or XML descriptor.

Type conversion of embeddable attributes.

Type conversion of collection members.

Type conversion of key/value of Map type persistent property.

Accept converter specification at a class level declaration.
EM 11.1.10, 11.1.11, 12.3
Not Started OPENJPA-???? Low Support adding named query via EntityManagerFactory.addNamedQuery() method EMF 3.10.14, 7.4
Not Started OPENJPA-???? High Entity Graph for query and find operations. Though OpenJPA has extensive support for fetch plans, the EntityGraph specification uses a rather different (and perhaps incomplete) way to define these subgraphs. It will be some work to translate the specification's way of defining these subgraphs to equivalent OpenJPA constructs.

The path navigation includes key field of a Map-type attribute. No equivalent exists in OpenJPA.

javax.persistence.loadgraph is similar to named fetch group concept.
Query 3.1.1, 3.2.7, 3.7, 7.4, 10.3, 12.2.3.17, 12.3
Not Started OPENJPA-???? High Support Schema Generation via Persistence bootstrap. Schema can be generated at startup both JSE and JEE environment. The schema can be generated both from entity mapping metadata and/or DDL scripts. A new set of properties javax.persistence.schema-generation.* can be passed via the Map argument while creating EntityManagerFactory.

The support exists in OpenJPA, but not as extensive as per the specification. Moreover the specified javax.persistence.schema-generation.* actions are to be mapped to the existing SchemaTool features.
Tools 8.2.1, 8.2.1.19, 9.2.1, 9.4, 9.4.1, 9.5.1, 9.7, 11.1.6, 11.1.19, 11.1.20, 11.1.23, 11.1.26, 11.2
Not Started OPENJPA-???? High New mapping annotations @Index, @ForeignKey are supported. Synonymous annotations are defined in OpenJPA. Query 2.13, 11.1.2, 11.1.8, 11.1.19, 11.1.23, 11.1.25, 11.1.26, 11.1.27, 11.1.35, 11.1.36, 11.1.44, 11.1.45, 11.2, 11.2.4
Not Started OPENJPA-???? High The version of persistence.xml is upgraded to 2.1. OpenJPA selects many default configurations based on the version of persistence.xml. These decisions points are to be checked for the new version. Parser 8.3, 12.3
Not Started OPENJPA-???? High Unwrap Cache, EntityManager etc. The EntityManager in the container had a derivation that supported unwrapping. That derivation may now be integrated with OpenJPA implementation. EM 3.1.1, 7.9.1, 7.10
Copyright © 2006,2013 The Apache Software Foundation. Licensed under Apache License 2.0.
Apache, the Apache feather logo and OpenJPA are trademarks of The Apache Software Foundation.
Other names may be trademarks of their respective owners.