geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Bauer" <techhu...@gmail.com>
Subject Updating the JPA spec jar for JPA 2.0
Date Mon, 10 Nov 2008 20:12:55 GMT
OpenJPA & Geronimo devs,
Efforts are underway to begin JPA 2.0 enhancements in OpenJPA.  OpenJPA
builds with and bundles the Geronimo JPA 1.0 spec jar.  As we move forward
to JPA 2.0, OpenJPA will need to use/provide updated spec APIs.  Like EJB
3.1, JPA 2.0 is still in the review stages so there may be frequent updates
to the spec API until the final draft is published.   This leads to
questions of "who, how, and where" for updating the JPA spec APIs to JPA
2.0.

IMHO, it would be best if the spec jar resides in Geronimo. Ideally, the
Geronimo project will have a branch for JPA 2.0 spec development, with the
OpenJPA project providing the JPA 2.0 enhancements.  The concern with that
approach is that the OpenJPA committers cannot commit to the Geronimo
repository.  OpenJPA would need committers on the Geronimo project to do
code commits and builds of the spec jar.  This may become a burden on the
Geronimo project and may be a potential (albeit small) bottleneck for
OpenJPA development.   Another alternative is for the OpenJPA project to
temporarily update and maintain the 2.0 spec API (using the current Geronimo
spec API as a starting point) while JPA 2.0 is in flux.  Major revisions
and/or the final could then be provided to Geronimo to be published in the
Geronimo repository, with the end goal of OpenJPA (and others) using the
spec jar provided by Geronimo.

Thoughts/ideas/opinions?

-Jeremy (OpenJPA committer)

Mime
View raw message