Then you reduce the usability of auto discovery.
Gavin King wrote:
Well, Hibernate will throw an exception if you try to map the same class
twice to the same entityName.
-----Original Message-----
From: Emmanuel Bernard [mailto:[EMAIL PROTECTED]
Sent: Friday, 19 August 2005 5:22 PM
To: Gavin King
Cc: Jordan Laughlin; hibernate-devel@lists.sourceforge.net
Subject: Re: [Hibernate] Configuration artifact precedence
And how do you compare a bunch (think inheritance) of hbms and a bunch
of annotated classes? Even a single cfg file and an annotated class? By
creating a specific comparison code? By creating the metamodel for both
and comparing them? All that work for an exception...
Gavin King wrote:
I must admit, that this makes sense to *me*....
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Jordan Laughlin
Sent: Friday, 19 August 2005 2:46 PM
To: hibernate-devel@lists.sourceforge.net
Subject: Re: [Hibernate] Configuration artifact precedence
Wouldn't it make sense for it to throw an exception if the mappings are
different, otherwise who cares? In migrating, if one makes a mistake it
would be good to know - "xxx has two different configurations" and not
pick one which has precedence (I'm coming from the standpoint of
someone who may be migrating soon). Unless, of course, the
configuration artifacts are always different between those mapped by
Annotations/ejb3xml and those mapped by hbm.xml. It would also
definately make sense if this was configurable.
I'm thinking out loud too :P
-JL
----- Original Message -----
From: "Max Rydahl Andersen" <[EMAIL PROTECTED]>
To: "Emmanuel Bernard" <[EMAIL PROTECTED]>
Cc: <hibernate-devel@lists.sourceforge.net>
Sent: Friday, August 19, 2005 5:23 AM
Subject: Re: [Hibernate] Configuration artifact precedence
Yes I know the problem - and I also didn't find any hint in the spec
about
how they plan to define the precedence with respect to ejb3 xml in
relation to annotations...any news on that ?
And I guess having precedence as something you can change to allow for
easier migration would be a good thing.
As it is now Annotations/ejb3xml wins first - correct ?
But couldn't we just say hbm.xml wins first and then users can remove
the
hbm.xml when they want the annotations to take over ? Or will that not
have any affect because the annotation
process occurs before users get the chance to add their hbm.xml
files...
Just thinking out loud...
/max
When Christian migrate CaveatEmptor to HEM, the encounters issues
with
the discovery mechanism, because there were no notion of precedence.
I
think the idea of configurable precedence came from here. I have to
admit I liked the idea to ease migrations. It's a bit like the BIOS
boot
ordering, you never used it, until you have to.
The problem is that I discover them in the jar file, they are not
added
by the user. So I have no idea of the ordering.
when will we ever have a user add both a hbm.xml AND ejb3xml file ?
And if we have - again, why not just choose the first one that gets
added to the configuration by the user ?
/max
Well, just to let you know and to help me to find a good
configuration property name.
What kind of values does it take ?
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle
Practices Agile & Plan-Driven Development * Managing Projects &
Teams *
Testing
& QA
Security * Process Improvement & Measurement *
http://www.sqe.com/bsce5sf
_______________________________________________
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle
Practices Agile & Plan-Driven Development * Managing Projects & Teams
* Testing
& QA
Security * Process Improvement & Measurement *
http://www.sqe.com/bsce5sf
_______________________________________________
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle
Practices Agile & Plan-Driven Development * Managing Projects & Teams *
Testing & QA Security * Process Improvement & Measurement *
http://www.sqe.com/bsce5sf
_______________________________________________
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle
Practices Agile & Plan-Driven Development * Managing Projects & Teams *
Testing & QA Security * Process Improvement & Measurement *
http://www.sqe.com/bsce5sf
_______________________________________________
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
