Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "EclipseLink/GettingStarted"

Line 5: Line 5:
 
=== Java Persistence API ===
 
=== Java Persistence API ===
  
=== Native ORM ===
 
  
=== Oracle TopLink ===
+
 
 +
=== Oracle TopLink's Native ORM ===
  
 
For those developers who have experience with or are already using Oracle TopLink's Native object-relational capabilities they will be able to easily convert their application over to use EclipseLink. The basic steps involved include:
 
For those developers who have experience with or are already using Oracle TopLink's Native object-relational capabilities they will be able to easily convert their application over to use EclipseLink. The basic steps involved include:
Line 17: Line 17:
 
=== Java XML Binding (JAXB) ===
 
=== Java XML Binding (JAXB) ===
  
=== Native MOXy ===
 
  
=== Oracle TopLink OXM ===
+
=== Oracle TopLink's Native OXM ===
  
 
For those developers who have experience with or are already using Oracle TopLink's Object-XML mapping capabilities they will be able to easily convert their application over to using EclipseLink.
 
For those developers who have experience with or are already using Oracle TopLink's Object-XML mapping capabilities they will be able to easily convert their application over to using EclipseLink.
  
 
# Migration of application code. Using the package-rename utility the application's source base can be automatically migrated from using the oracle.toplink* packages to using the org.eclipse.persistence.* packages.
 
# Migration of application code. Using the package-rename utility the application's source base can be automatically migrated from using the oracle.toplink* packages to using the org.eclipse.persistence.* packages.

Revision as of 10:09, 5 October 2007

This page will focus on helping new users to get started with EclipseLink. It will have a sub-section/page per persistence services walking through its basic configuration and usage.

Object-Relational

Java Persistence API

Oracle TopLink's Native ORM

For those developers who have experience with or are already using Oracle TopLink's Native object-relational capabilities they will be able to easily convert their application over to use EclipseLink. The basic steps involved include:

  1. Migration of application code. Using the package-rename utility the application's source base can be automatically migrated from using the oracle.toplink* packages to using the org.eclipse.persistence.* packages.

MOXy: Object-XML

Java XML Binding (JAXB)

Oracle TopLink's Native OXM

For those developers who have experience with or are already using Oracle TopLink's Object-XML mapping capabilities they will be able to easily convert their application over to using EclipseLink.

  1. Migration of application code. Using the package-rename utility the application's source base can be automatically migrated from using the oracle.toplink* packages to using the org.eclipse.persistence.* packages.

Back to the top