Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
EclipseLink/Development/JPA 2.0/metamodel api
JPA 2.0: MetaModel API
| Date | Committer(s) | Description |
|---|---|---|
| March 3, 2009 | gyorke | Initial feature template |
| March 3, 2009 | mobrien | Start analysis |
Summary
In JPA 2.0 the specification has defined standard APIs for representing the structure of a persistence unit model. This is referred to at the MetaModel APIs. There are two main aspects to providing this functionality. The first is the runtime model accessed from EntityManagerFactory.getMetaModel() and the second is the APT generated meta model classes. Our first goal is to provide functionality for runtime access.
For details see section 5.2 and 5.3 of Proposed Final Draft.
Work Estimate
- Investigate EclipseLink Metamodel
- approx 3 days
- Develop implementations of MetaModel or refactor current metamodel
- approx 10 days
- APT investigation and prototype
- approx 5 days
- APT tooling/testing
- approx 10 days
Analysis
Concepts
Metamodel?
- In the context of EclipseLink a metamodel is an abstract view of the managed classes in the persistence unit.
- We use the metamodel to construct a runtime query structure that is "object-based".
Relation to JPQL?
Functional Requirements
Requirements and constraints have traceability down to their associated use cases.
Requirements Table
| Req# | A# | Use Cases# | Description |
|---|---|---|---|
| R1 | - | - | Support runtime Metamodel APIs |
| R1.1 | - | - | |
| R2 | A1 | - | Support APT generation of Canonical Metamodel classes |
| R2.1 | - | - | No extra runtime paramenters are required beyond existing -javaagent runtime flag |
Assumptions Table
| A# | Req# | Use Cases# | Description |
|---|---|---|---|
| A1 | - | - | Java 5 is the minimum compile target we support (unchanged) |
| A2 | - | - | Runtime environment for metamodel construction is SE and compilation time only |
Constraints Table
| C# | A# | Use Cases# | Description |
|---|---|---|---|
| C1 | - | - | Dependency on the APT tool specific to the SUN JDK 1.5.0?
Determine if we are ok running on the IBM J9 JVM in SE mode. |
Design
API
Metamodel and Criteria packages interfaces API
The following static UML class diagram that illustrates the relationship between the Criteria and Metamodel API's will serve as a basis for the metamodel API part of this work.
Annotation Processors
We require a design time annotation processing tool to create metamodel class files X_.
APT
APT is the annotation processing tool that has been shipped since Java 5.
Design Criteria
Security
Concurrency
Performance
Configuration
Use Cases
Use cases have traceability back to their requirements and constraints via their id# and have a 1-1 correspondence with test cases.
| Use Case ID# | Assumptions# | Requirements# | Description |
|---|---|---|---|
| UC1 | - | - | Construct object-based query definition object |
Concrete Use Cases
Details on each use case.
UC1:
- Preconditions
- Postconditions
- Path
- Exceptions
Variant Use Cases
Details on each variant (negative test) use case.
Implementation
Module Reuse
How much of the existing JPA annotation processor will be used or transitioned?
Modified Modules
New Modules
Testing
Open Issues
This section lists the open issues that are still pending that must be decided prior to fully implementing this project's requirements.
| Issue # | Owner | Description / Notes |
|---|---|---|
Decisions
This section lists decisions made. These are intended to document the resolution of open issues or constraints added to the project that are important.
| Issue # | Description / Notes | Decision |
|---|---|---|
Documentation
Wiki and formal documentation links here.
Future Considerations
During the research for this project the following items were identified as out of scope but are captured here as potential future enhancements. If agreed upon during the review process these should be logged in the bug system.