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
