Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/Examples/JPA/Migration/Kodo"
< EclipseLink | Examples | JPA | Migration
m (→Migration of Kodo to EclipseLink) |
m (→Migration of Kodo JDO to EclipseLink JPA) |
||
Line 7: | Line 7: | ||
==Migration of Kodo JPA to EclipseLink JPA== | ==Migration of Kodo JPA to EclipseLink JPA== | ||
==Migration of Kodo JDO to EclipseLink JPA== | ==Migration of Kodo JDO to EclipseLink JPA== | ||
+ | |||
+ | * Kodo supports the mapping of native sql query results to non-Entity POJOs. This is similar to the use of constructor expression in JPQL queries except the query is a native one. The restriction on making this work in Kodo is that the names of the result set columns must match the names of the attributes of the POJO. | ||
==References== | ==References== | ||
*Nov 2005 - BEA acquires the object persistence company [http://www.solarmetric.com/solarmetric_jump_page/ SolarMetric Inc.] and Kodo which supports EJB 3.0 and JDO | *Nov 2005 - BEA acquires the object persistence company [http://www.solarmetric.com/solarmetric_jump_page/ SolarMetric Inc.] and Kodo which supports EJB 3.0 and JDO | ||
*Apr 2008 - Oracle acquires [http://www.oracle.com/corporate/press/2008_apr/bea-closes-rls.html BEA] | *Apr 2008 - Oracle acquires [http://www.oracle.com/corporate/press/2008_apr/bea-closes-rls.html BEA] |
Revision as of 09:52, 24 September 2009
Contents
Migration of Kodo to EclipseLink
Purpose
Started 20090212 - under construction
This page will detail steps and issues surrounding migration from the Kodo JPA or JDO API's to EclipseLink JPA. It is a work in progress and will involve more familiarization with Kodo JDO.
Migration of Kodo JPA to EclipseLink JPA
Migration of Kodo JDO to EclipseLink JPA
- Kodo supports the mapping of native sql query results to non-Entity POJOs. This is similar to the use of constructor expression in JPQL queries except the query is a native one. The restriction on making this work in Kodo is that the names of the result set columns must match the names of the attributes of the POJO.
References
- Nov 2005 - BEA acquires the object persistence company SolarMetric Inc. and Kodo which supports EJB 3.0 and JDO
- Apr 2008 - Oracle acquires BEA