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?
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?
3. Are there any significant ORM-feature differences between WO and JP?
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?
5. JP seems to rely heavily on annotations. I have never worked much
with annotations... What are your experiences with this approach?
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?
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., [email protected]
wrote:
From: Stamenkovic Florijan <[email protected]>
Date: 9 de abril de 2009 04:29:12 p.m. GMT-05:00
To: David Avendasora <[email protected]>
Cc: Development WebObjects <[email protected]>
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 protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
