A Technology Project Proposal [updated June 21st 2005]
The JSR220-ORM Project's goal is to provide tooling for an implementation of the JSR 220 persistence and JSR 243 specifications integrated with the Eclipse platform. Further, the goal of the project is to track the changes to these specifications, so that in addition, as they merge together towards a common persistence standard, appropriate tooling will be fully implemented by this project. The over arching goal of this project is to provide visual development tools that facilitate round trip engineering when using the JSR 220/243 approach to persistence. Further, to provide an implementation that is extensible to accommodate new types of input and generate artifacts for alternative runtimes.
The JSR220-ORM Project is directly tied to the JSR 220 and 243 specifications. Further it will undoubtedly have dependencies on or provide dependencies to other sub projects within the Eclipse Data Tools Project and Web Tools Project . Additionally, elements of the project will depend on JDK 1.5 for annotation support required in JSR 220.
Milestone 1 plan: April 18th, 2005 Release initial Versant Open Access - 4.0 commercial implementation of EJB 3.0 and JDO 2.0 ( JSR 220/243 ) to the open source community which includes initial Eclipse integration ( lacking integration with other Data Tool Projects ) for public review, comment and contribution. This is a proposal phase opportunity for the community to provide feedback on the tooling and get involved.
Milestone 2 plan: August 8th, 2005 Release an Eclipse platform integrated version which is using core code components of other relevant Eclipse sub-projects including but not limited to Data Tools Project and Web Tools Project .
The goal of this milestone is to provide:
Image 1: The following block diagram gives an overview of the tooling approach and to integration with the Eclipse platform.
Milestone 2 use case coverage:
Image 2: The following Eclipse screen shots give an idea of the developer experience and feature set of the Milestone 2 plug-in.
Milestone 3 plan: October 2005 Release updates that include complete support for reverse engineering of existing relational schema, EJBQL visual query builder, support for named queries, support for custom fetch group configuration.
Milestone 3 use case coverage:
The above Milestones are visible and achievable. Other elements including Data Tools Project and Web Tools Project integration and changes in the evolving JSR 220 specification are less definite. As the months progress, it is expected that these other issues will become clearer and community involvement will be better understood so that ongoing milestones can be established. It is also expected that community involvement will reprioritize deliverables and timelines of milestones