Jump to: navigation, search

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

m (New page: =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 tha...)
 
m (=Retrofiting an existing Java SE appliction to use Derby)
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.
==Retrofiting an existing Java SE appliction to use Derby=
+
==Retrofiting an existing Java SE appliction to use Derby==
 
===Add persistence.xml===
 
===Add persistence.xml===
 
===Add derby jars===
 
===Add derby jars===
 +
 
=References=
 
=References=
 
*Originated 20091113
 
*Originated 20091113

Revision as of 12:14, 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.

Retrofiting an existing Java SE appliction to use Derby

Add persistence.xml

Add derby jars

References

  • Originated 20091113