I want to have it renamed (if at all) before the next release to be
able to freeze the "api".
I'm leaning to change it to hbm2<whatever> for consistency and
recognization value, but not sure...
any input welcome ;)
The names are fine. You won't find a better schema for so many different
things. In fact, the only thing we have to change, and I've done that
for a while now, is to tell users that "hbm" does not mean Hibernate
mapping file, but "hibernate metadata" or "hibernate metamodel".
yes, makes sense. I'll stick to hbm2x.
But should we change cfg2cfgxml and cfg2hbm to hbm2cfgxml and hbm2hbm
then ?
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
[EMAIL PROTECTED]
http://hibernate.org
JBoss Inc
[EMAIL PROTECTED]
http://www.jboss.com/events/jbossworld
JBoss World Barcelona 10-12 October
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
