Re: [OT] local persistence ORM
Re: [OT] local persistence ORM
- Subject: Re: [OT] local persistence ORM
- From: Daniel Mejía <email@hidden>
- Date: Fri, 10 Apr 2009 20:51:00 -0500
Florijan,
On 10/04/2009, at 10:10 a.m., Stamenkovic Florijan wrote:
Hi Daniel,
This looks quite interesting... JavaPersistence's API makes much
more sense to me then JDO's. I have some questions about JP however,
if you have a moment to answer them:
1. How complicated is the glue layer between JP, and MSAccess / Derby?
In my experience its very easy to intregrate Derby withh JP. For
simple programs NetBeans has some wizards that do all the job to
create the Java Class with all the annotations required to do a CRUD
programs.
2. Do you have to define the database schema on both layer manually?
Or is there some sort of an automation involved in this process?
You have two option to define the database schema. You can use
NetBeans to do a reverse enginering and get al lthe required Beans for
the tables that you need. Also, you can use the modeler to define a
model (like EOModeler) to get the XML file with the definitions of you
schema (Entities, attributes, relatiions, etc.). With JP you can merge
both definitions you you need to modify you XMl schema using
annotations.
3. Are there any significant ORM-feature differences between WO and
JP?
I don't know if there are significant differences, but I have found
very similar JPA with EOF.
4. Can JP conveniently deliver info on the database shema? Info such
as a list of properties, attributes, relationships, inverse
relationships, attribute classes... Or maybe does one have to
manually extract that from the annotations using reflection?
All that info is defined using annotations of XML files.
5. JP seems to rely heavily on annotations. I have never worked much
with annotations... What are your experiences with this approach?
You can use a XML file ass with EOF to define all the definition of
your database and also you can use annotations in your Beans or both.
6. JP seems to required quite a bit of typing to define even the
simplest entities. Do you have problems with scaling, when defining
a complex schemas?
You don't need to type anything. For simple programs you can use the
NetBeans wizard to get the Java Classes ( http://wiki.netbeans.org/SimpleJPAApplicationWithNetbeans
), For more complex project you can use the Workbench to define your
schema. http://wiki.eclipse.org/Using_Workbench_(ELUG)
Thanks,
F
On Apr 09, 2009, at 23:03, Daniel Mejía wrote:
Hi,
To have persistence in the client I'm using the JavaPersistence API
with NetBeans. Here you can find an example with MS Access, but
also works fine with Derby.
http://wiki.netbeans.org/JavaPersistenceApi
Saludos,
Daniel.
On 09/04/2009, at 07:35 p.m., webobjects-dev-
email@hidden wrote:
From: Stamenkovic Florijan <email@hidden>
Date: 9 de abril de 2009 04:29:12 p.m. GMT-05:00
To: David Avendasora <email@hidden>
Cc: Development WebObjects <email@hidden>
Subject: Re: [OT] local persistence ORM
Nope...
1) I am not allowed to bundle all of WO into my client app.
2) This should be light-weight. Both in terms of the API and the
library size. WO is neither.
Thx,
F
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden