blob: 967c7addeb12e205939ef685080edcbccba91985 [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<TITLE>JSR220-ORM Project Plan</TITLE>
<META http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<LINK href="Plan_files/eclipse.css" type="text/css" rel="stylesheet">
<META content="MSHTML 6.00.2800.1400" name="GENERATOR"></HEAD>
<BODY text="#000000" vLink="#551a8b" aLink="#ff0000" link="#0000ee" bgColor="#ffffff">
<TABLE cellSpacing="5" cellPadding="2" width="100%" border="0">
<TBODY>
<TR>
<TD align="left" width="60%"><FONT class="indextop"></FONT><STRONG><FONT face="Verdana" size="6">JSR220-ORM
Plan</FONT></STRONG><BR>
<FONT class="indexsub">A Technology Project Proposal [updated&nbsp;April
13&nbsp;2005]</FONT></TD>
<td width="40%"><img height="86" hspace="50" src="/images/Idea.jpg" width="120" align="center"></td>
</TR>
</TBODY></TABLE>
<TABLE cellSpacing="5" cellPadding="2" width="100%" border="0">
<TBODY>
<TR>
<TD vAlign="top" align="left" bgColor="#0080c0" colSpan="2"><B><FONT face="Arial,Helvetica" color="#ffffff">Introduction</FONT></B></TD>
</TR>
<TR>
<TD>
<P>The JSR220-ORM Project's goal is to provide a 100% compliant 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, it will be fully implemented by this project. Finally,
the goal is to provide visual development tools that facilitate round trip
engineering when using the JSR 220/243 approach to persistence.</P>
<P>&nbsp;</P>
</TD>
</TR>
</TBODY></TABLE>
<TABLE cellSpacing="5" cellPadding="2" width="100%" border="0">
<TBODY>
<TR>
<TD vAlign="top" align="left" bgColor="#0080c0" colSpan="3"><B><FONT face="Arial,Helvetica"><FONT color="#ffffff">Dependencies</FONT></FONT></B></TD>
</TR>
<TR>
<TD colSpan="3">
<P>The JSR220-ORM Project is strictly 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&nbsp;for
annotation support required in JSR 220.</P>
<P>&nbsp;</P>
</TD>
</TR>
</TBODY></TABLE>
<TABLE cellSpacing="5" cellPadding="2" width="100%" border="0">
<TBODY>
<TR>
<TD vAlign="top" align="left" bgColor="#0080c0"><B><FONT face="Arial,Helvetica"><FONT color="#ffffff">Milestones</FONT></FONT></B></TD>
</TR>
<TR>
<TD>
<P><STRONG>Milestone 1 plan:</STRONG> 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.&nbsp;&nbsp; This is a proposal phase opportunity for the
community to provide feedback and get involved.</P>
<P><STRONG>Milestone 2 plan:</STRONG> June 1st, 2005 Release remaining intended
functionality of current Versant Open Access 4.0 stand alone visual development
tooling, including remaining elements of round trip engineering, visual query
builder and object viewer into a fully integrated Eclipse plugin. Release full
EJBQL capabilities for JSR 220 support. Present a plan for integrating other
identified areas of overlap with other Eclipse projecting including but not
limited to <A href="/proposals/eclipse-dtp/main.html">Data
Tools Project</A> and&nbsp;<A href="/webtools/">Web Tools
Project</A> . Provide review of any new JSR 220 drafts that affect future
milestones.
</P>
<P><STRONG>Milestone 3 plan:</STRONG> August 2005 Release JSR 220 updates that
include implementation of all JSR 220 defaults, implementation of JSR 220 meta
data for object relational mapping where different from JSR 243. Deliver
removal of all vendor specific extensions relating to JSR 243 preview
functionality.
</P>
<P>The above Milestones are visible and achievable. Other elements including&nbsp;<A href="/proposals/eclipse-dtp/main.html">Data
Tools Project</A> and&nbsp;<A href="/webtools/">Web Tools
Project</A>&nbsp; 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
</P>
<P>&nbsp;</P>
</TD>
</TR>
</TBODY></TABLE>
</BODY>
</HTML>