[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[List Home]
|
Re: [eclipselink-users] [OT]-ish Reading Annotation Data
|
- From: Tim Hollosy <hollosyt@xxxxxxxxx>
- Date: Tue, 29 Sep 2009 07:26:17 -0400
- Delivered-to: eclipselink-users@eclipse.org
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=zuaC7daouAFhTGzbROe1RTIrkxvyBzDBaFkjaYBy1Uk=; b=RNi9/gRIky2tXIyAfg4JeIHWE8yjw3N6nszs/7zOeyNsha8AxYhv7sEaRauzMVbV1k dL6f84fiAKC/m1edbInfxdneTKJ4o4pAgIKRiClf9GJfIwk7dY75CBhIpSN3XDowZYUn q4fl09IftDCbRa0Eof/s3r8RqxrcYZccvkAfk=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=XochmpAOvdjW53Ry0uAr+l8y6CxuL73q4ULKo5mmmw8FQA+tjKpOFK7BGl5L5lKebX Rsz2jbS53IohDxaDCdPjC58DhAXiaK9xqQHco/y6H7QuIqjdh3LDWdk250irshVZ9VOR C2fn8YQlsT+A3UcVCRRuywYwHNjGOFHVg/Cr0=
The idea of having a POJO based entity layer like we have in JPA is
that those same entities that you define once for JPA can and should
be used for other things -- like holding form values in a web
framework, etc.
./tch
On Tue, Sep 29, 2009 at 6:41 AM, RogerV <roger.varley@xxxxxxxxxxxxxx> wrote:
>
>
>
> mobrien wrote:
>>
>> We welcome any suggestions on extending the JPA 2.0 API implementation.
>> I will add extended annotation access to the design page at
>> http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/metamodel_api
>>
>
> Hi Michael
>
> I'm coming from being a long term developer on IBM S/38's, AS/400's and
> latterly on SAP R/3 systems. These systems all had a "meta layer" that sat
> between the application and the database - a definition repository or a data
> dictionary if you like. This allowed you to define your data elements once
> and once only. So you could define your customer number for example as a 9
> digit integer field. You could then define other fields in terms of them
> being a "Customer Number" type. Not only could you define the type & size,
> you could set default values, display/print formatting rules, text that
> would be used as labels when displaying/printing, text that would be used as
> help text (tooltips would, I guess, be the java equivalent). The
> "disadvantage" I see with JPA & Java, at the moment is that this information
> (for example element length) is often defined in multiple locations - it's
> in the DB table definitions, it's in the entity annotation, it's in the
> validation code/framework and it's often in the html/css definitions as
> well.
>
> So I'm wondering if the idea of a "data dictionary" would be of more use.
> I've no idea whether this concept would be a welcome addition to
> EclipseLink, or even if it's physically possible. All I can say having used
> such systems, that it brings consistancy to displays and reports, eliminates
> definition duplication, makes data changes simple to implement application
> wide and generally makes life easier.
>
>
>
> Regards
>
>
>
> --
> View this message in context: http://www.nabble.com/-OT--ish-Reading-Annotation-Data-tp25645176p25660646.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
>