Difference between revisions of "EclipseLink/Examples/JPA/Derby"

From Eclipsepedia

Jump to: navigation, search
m (References)
m (Running EclipseLink on the Derby Database)
Line 2: Line 2:
 
*Running EclipseLink on derby has several advantages including ease of installation and small footprint for rapid development - and the fact that it is also open source like EclipseLink.
 
*Running EclipseLink on derby has several advantages including ease of installation and small footprint for rapid development - and the fact that it is also open source like EclipseLink.
 
*This tutorial is currently working with Derby 10.5.3.0.
 
*This tutorial is currently working with Derby 10.5.3.0.
==Retrofiting an existing Java SE appliction to use Derby==
+
==Retrofitting an existing Java SE application to use Derby==
 
===Add persistence.xml===
 
===Add persistence.xml===
 +
 
===Add derby jars===
 
===Add derby jars===
  
 
==References==
 
==References==
 
*Originated 20091113 for Derby 10.5.3.0
 
*Originated 20091113 for Derby 10.5.3.0

Revision as of 14:45, 1 December 2009

Contents

Running EclipseLink on the Derby Database

  • Running EclipseLink on derby has several advantages including ease of installation and small footprint for rapid development - and the fact that it is also open source like EclipseLink.
  • This tutorial is currently working with Derby 10.5.3.0.

Retrofitting an existing Java SE application to use Derby

Add persistence.xml

Add derby jars

References

  • Originated 20091113 for Derby 10.5.3.0