| Why choose EclipseLink rather than vinilla JPA, e.g. TopLink, Hibernate etc. [message #11971] |
Mon, 30 June 2008 17:25  |
Eclipse User |
|
|
|
Hi,
Please allow me to introduce myself, I am Joel and I am co-lead of the
new EF project technology.ormf. We have been approved and provisioning
is progress so the web is not set up yet, but I believe it will be
http://www.eclipse.org/ormf/
Now that we have been approved I am beginning to explore some of the
architectural changes I am considering. One of my key initial goals is
to lighten up the deployment requirements. Presently it requires a J5EE
server and it is simply overkill. So in the first instance I want to
reengineer it as a web application so only Tomcat, Jetty, et. al. are
necessary. As a future step I plan on exploring deploying on top of
OSGI (Equinox).
The architecture already uses JPA, Toplink Essentials as a matter of
fact as I am developing with Glassfish.
So my question boils down to why should I choose EclipseLInk over a
plain old JPA provider? I love the idea that EclipseLink supports XML,
SDO, EIS, as well as RDBM. I am also really attracted to the fact that
it is a part of the Eclipse family of projects. But the question is am
I over engineering?
Apologies if this has been covered before, but alas the old threads are
no longer available. Btw, would this perhaps be a reasonable addition
to the FAQ: Why choose EclipseLink?
All the best and thanks,
Joel
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Too
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
|
| Re: Why choose EclipseLink rather than vinilla JPA, e.g. TopLink, Hibernate etc. [message #563930 is a reply to message #11971] |
Tue, 01 July 2008 04:17  |
| Eclipse User |
|
|
|
Joel,
EclipseLink is a JPA provider. It just also happens to leverage the same
core mapping 'engine' to address other data sources/types. EclipseLink is
replacing TopLink Essentials as the reference implementation of JPA in 2.0
and has already replaced it within GlassFish V3. We believe, based on our
long commercial history with Oracle TopLink, that EclipseLink is the most
mature object-relational solution available and is the best JPA
implementation (open-source or otherwise).
If you are already using TopLink Essentials then the upgrade to
EclipseLink should be very straight forward. We would be happy to help
with any specific feature or usage questions you encounter along the way.
Doug
Recent Article: http://eclipse.dzone.com/articles/introducing-eclipselink
|
|
|
|
Powered by
FUDForum. Page generated in 0.03435 seconds
Home