[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipselink-users] getting started
|
We have a mixed team of Eclipse & IntelliJ, so the ideal solution would
simply be something that is not IDE dependent ( like a Java tool ). We
have three DB's (or schemas or sets of tables), so a tool for generating
the entity classes to get started on a large set of tables would be
helpful, otherwise one person that uses Eclipse would be assigned the
task and own that piece of doing all the work to get started on all
three DB's.
If there is not a tool, I could look at Dali and pull the ideas out into
a java tool that is driven by command line options or by a .properties
or .xml file, but thought I would check to see what is out there, if
anything.
J.V.
On 6/1/2012 10:00 AM, eclipselink-users-request@xxxxxxxxxxx wrote:
Today's Topics:
1. Re: eclipselink - getting started (Neil Hauge)
----------------------------------------------------------------------
Message: 1
Date: Fri, 01 Jun 2012 10:45:47 -0400
From: Neil Hauge<neil.hauge@xxxxxxxxxx>
To: eclipselink-users@xxxxxxxxxxx
Subject: Re: [eclipselink-users] eclipselink - getting started
Message-ID:<4FC8D59B.2020805@xxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
J.V.
You should take a look at the Eclipse Dali[1] tools, especially if you
are an Eclipse IDE user. If you are using NetBeans, there are JPA
entity generation tools included there as well.
Dali will handle generating the relationships and will actually show you
what it is going to generate before completing the wizard. Support for
generating entities with inheritance is not supported in Dali, and I'm
not aware of any JPA tools that support doing this. My recommendation
would be to refactor the code after generation to improve the model.
Supporting the four databases shouldn't be a problem, as this will be
handled by EclipseLink at runtime. You may want to review your java
attribute types in the wizard to be sure that the java types being used
are satisfactory for your application.
Dali has a lot of specific support for EclipseLink, so if you are
interested in EclipseLink JPA tooling, I highly recommend checking it
out. Dali is available in the main Eclipse update sites for Indigo or
Juno versions, and comes installed in the Eclipse Java EE Packages.
If you need additional help with Dali, you can find more support at the
Dali forum[2].
[1] http://www.eclipse.org/webtools/dali/
[2] http://www.eclipse.org/forums/index.php/f/113/
Neil
On 5/31/2012 6:44 PM, J.V. wrote:
We are currently using the old method of using hibernate ( .xml files
) - no JPA.
I want to convert over to EclipseLink. We have three schemas/DB's and
about 300 tables. What is the best way to generate entity classes for
each table and:
1. have the relationships (many to many) autoconfigured?
2. have all the entity classes extend from a specific base class
that I create where I want to have some default behaviour for each
entity?
It would be grueling to create all the entity classes by hand and
generating these from the DB would be most helpful.
Also we will be use the generate model with four databases on which
our product is built (Oracle, PostgreSQL, SQL Server& MySQL), so the
generated types must take into consideration the different database
types and map correctly.
I would like to generate the classes from an installation of
PostgreSQL and have it work with the four DB's that we support.
if this is at all possible, please point me in the right direction.
thanks
J.V.
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
------------------------------
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
End of eclipselink-users Digest, Vol 58, Issue 2
************************************************
