is in one place. cross-referencing between mappings and sourcecode is always a
pain, especially since my IDE can't help me. Note also that we reduce total LOC,
since more info can be inferred from the context of the annotation.
Actually, I always wanted something like this for Hibernate. I originally went with
XML metadata only with very strong reservations. I am an XML-sceptic - and I
know you are too Christian, so don't front ;)
Christian Bauer wrote:
On 07 Apr (16:30), Emmanuel Bernard wrote:
Here is a simple example which widely use default values of each annotations, and thus not expressed (actually hbm does the same).
I haven't read the spec fully, but what is the point of this annotation stuff anyway? It's not like putting metadata in source files helps much, it makes it harder to read and you have a new obscure syntax to learn and remember.
As Scott Stark said some months ago: I'll use it when there is a mechanism that allows me to have metadata _separate_ from source files, but easily applicable, so I can have a set of metadata information for each class and pick one for my current case. Don't mix source and metasource.
-- Gavin King +61 410534454
Hibernate [EMAIL PROTECTED] http://hibernate.org
JBoss Inc [EMAIL PROTECTED] http://jboss.com
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
