[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [eclipselink-users] project.xml and JPA annotations
|
My project also need intermediate steps for the same kind of migration.
What I will do when I have time is to dump the memory representation to
an arbitrary XML (see XStream) then it's easy to compare to see what
need to be fixed. I doubt lot of initialization runtime code is needed
to fix the gap. Even if it's lot of classes, at the end of the day it's
the same pattern and "node" in the definition tree.
I would have preferred that this is already done part of EclipseLink
supported features. Well, EclipseLink seem having a small user base; we
often feel we are the first, second, or only user of many features.
-----Original Message-----
From: eclipselink-users-bounces@xxxxxxxxxxx
[mailto:eclipselink-users-bounces@xxxxxxxxxxx] On Behalf Of fcalfo
Sent: Monday, April 27, 2009 6:45 PM
To: eclipselink-users@xxxxxxxxxxx
Subject: Re: [eclipselink-users] project.xml and JPA annotations
Guy Pelletier wrote:
>
> Unfortunately no, that functionality is not supported at this time.
Are
> there specific configurations that you want from the project.xml?
>
>
We've got an existing application with about 400 classes mapped in a
TopLink
9 Workbench project that we're trying to migrate to JPA/EclipseLink. So
we're looking for intermediate steps we can take to hopefully avoid
migrating them all at once. We were hoping to gradually annotate
classes
while using the mappings from the workbench until they're all migrated.
--
View this message in context:
http://www.nabble.com/project.xml-and-JPA-annotations-tp23262131p2326683
3.html
Sent from the EclipseLink - Users mailing list archive at Nabble.com.
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
