Motivations    1. OJB is an inactive product           * one developer remaining           * much less activity and resources then some of the other offerings out there which support JPA such as Hibernate and Toplink           * last release was in December 2005    2. JPA is part of the standard Java platform, OJB is not.    3. JPA is pluggable, allowing for usage of a different JPA implementation if desired.    4. Kuali Student is already using JPA Statement of Direction The TRC JPA Working Group is recommending the following steps for proceeding with adding JPA support to Rice and the other Kuali projects:    1. JPA 2.0 will be the target version of JPA    2. We will use Hibernate as the reference implementation    3. We will try to stick to the JPA specification as much as possible           * Where needed, Vendor-specific (Hibernate) features should preferably be implemented through configuration properties/xml rather than annotations    4. Changes will have to be made to the API and so this will be an impacting change in Rice    5. This needs to be coordinated with other Kuali Project release schedules    6. We will will include a Criteria API in the converted version of Rice    7. We recommend removing OJB support when Rice is converted to JPA    8. Each project will identify a representative from their team to participate in the development of the JPA framework infrastructure in Rice.    9. Rice team (in conjunction with contributed Kuali project resources) will:           * work on any required analysis and development to implement JPA support in Rice           * develop documentation on conversion guide and best practices           * deliver a basic conversion script                 o focus will be on the straightforward OJB to JPA conversion items to save projects time doing manual conversion and will not be a complete OJB to JPA conversion           * work on completion of converting Rice internally to use JPA           * work with the other Kuali project teams to enact a conversion from OJB to JPA