Jump to: navigation, search

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

m (=Retrofiting an existing Java SE appliction to use Derby)
m (Running EclipseLink on the Derby Database)
Line 1: Line 1:
 
=Running EclipseLink on the Derby Database=
 
=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.
 
*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.
 
==Retrofiting an existing Java SE appliction to use Derby==
 
==Retrofiting an existing Java SE appliction to use Derby==
 
===Add persistence.xml===
 
===Add persistence.xml===

Revision as of 12:17, 13 November 2009

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.

Retrofiting an existing Java SE appliction to use Derby

Add persistence.xml

Add derby jars

References

  • Originated 20091113