|
Mike,
The
Dali project is focussed on delivering rich JPA tooling within WTP. We plan to
work closely with the Dali project team to ensure EclipseLink is well supported.
We definitely see the ORM space evolving towards
JPA+extensions and believe that the Dali project will address this need within
the Eclipse IDE space.
The
proposed addition of the Workbench to the EclipseLink project would address
native EclipseLink object-relational, object-xml, object-non-relational
(EIS/JCA) as well as JAXB development support. This is basically bringing the
equivalent mapping capabilities of the Oracle TopLink product to developers
using EclipseLink.
Our
short term goal for contributing the workbench tool to the EclipseLink project
is to address the immediate need for native ORM and non relational mapping. This
will facilitate quickly expanding the user base to include current Oracle
TopLink customers as well as providing mapping support for non-JPA
usage. In the longer term we want to have this mapping
functionality evolve to better integrate and leverage other projects of the
Eclipse ecosystem expanding overall persistence mapping
capabilities.
Doug
Some
threads showing community interest in this:
So
what would be the relationship of this Mapping Workbench component and the
Dali JPA tooling project?
From:
technology-pmc-bounces@xxxxxxxxxxx [mailto:technology-pmc-bounces@xxxxxxxxxxx]
On Behalf Of Doug Clarke
Sent: Friday, September 21, 2007
11:00 AM
To: Technology PMC;
eclipselink-dev@xxxxxxxxxxx
Subject: RE: [technology-pmc] New
component in EclipseLink - needs to follow the proper
process
Thanks
for keep an eye on us. I do appreciate it as we learn our way within the
ecosystem and its processes.
The
email referenced was sent at my request to ensure that all of the developers
are aware that this is planned and so the internal developers can start
preparing the code contribution in an agreed upon format. I wanted to have the
opportunity for a discussion concerning the project's package and SVN
structure.
We
will definitely be following all of the processes prior to checking in any
code or creating any new components.
-----Original
Message-----
From: technology-pmc-bounces@xxxxxxxxxxx
[mailto:technology-pmc-bounces@xxxxxxxxxxx]On Behalf Of Bjorn
Freeman-Benson
Sent: Friday, September 21, 2007 10:42
AM
To: eclipselink-dev@xxxxxxxxxxx;
technology-pmc
Subject: [technology-pmc] New component in
EclipseLink - needs to follow the proper process
Doug et al,
I noticed this email (http://dev.eclipse.org/mhonarc/lists/eclipselink-dev/msg00044.html)
saying that you are going to have a new component in the EclipseLink
project. Please note that you need to follow the appropriate processes,
specifically:
- Getting
approval from the PMC.
- Notifying
the membership of new contributions: http://www.eclipse.org/projects/dev_process/notifying-membership.php
- Any
external code contributions must go through the Eclipse Legal review
starting with the Contribution Questionnaire and may not be put into
CVS/SVN until approval is received.
-
Bjorn
|
