| Why choose EclipseLink rather than vinilla JPA, e.g. TopLink, Hibernate etc. [message #563901] |
Mon, 30 June 2008 21:25 |
|
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]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
Powered by
FUDForum. Page generated in 0.02944 seconds
] 
Search
Help
Register
Login
Home
