openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey (JIRA)" <>
Subject [jira] Updated: (OPENJPA-317) API formalization pre-1.0
Date Mon, 20 Aug 2007 06:43:30 GMT


Patrick Linskey updated OPENJPA-317:

    Attachment: OPENJPA-317.patch

OPENJPA-317. Changed OpenJPA published API pre-1.0. Reduced the scope of the dependencies
in OpenJPAEntityManager and the other published interfaces; converted JDK1.4-style symbolic
constant usage to new enums; changed some method names for clarity and consistency; removed
old javax.resource dependencies; updated @published and @nojavadoc tags. The published interfaces
should now only reference other published interfaces in method signatures, and it should be
possible to build javadoc for just the published interfaces.

Removed getDelegate() calls from the published interfaces, as they expose internals. They
are still available on the impl classes themselves, or the SPI ifaces when available.

Added covariant return types to JDBCFetchPlan.

Changed BrokerFactoryListener interface to not encode event types in the listener signature.

Moved some methods from OpenJPAPersistence to JPAFacadeHelper.

to-do: maybe move tx stuff to new OpenJPATransaction interface that does not extend EntityTransaction?
(can't keep in subtype of EntityTx because getTx() fails in a JTA context), other event changes?

We will need to grow these published interfaces to provide access to some things in the internal
interfaces. However, these interfaces will remain stable moving forward within the constraints
of the OpenJPA deprecation policies.

> API formalization pre-1.0
> -------------------------
>                 Key: OPENJPA-317
>                 URL:
>             Project: OpenJPA
>          Issue Type: New Feature
>          Components: jpa
>    Affects Versions: 0.9.0, 0.9.6, 0.9.7
>            Reporter: Patrick Linskey
>             Fix For: 1.0.0
>         Attachments: OPENJPA-317.patch
> This issue tracks the effort to formalize and optimize our API prior to the 1.0 release.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message