<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<blockquote
cite="mid:42FEEA91-1629-47D9-8547-98544D3D6CD7@hibernate.org"
type="cite">
<div>
<blockquote type="cite">
<div style="">
<div>It's a clusterfuck, sorry about that. We are all wrong except
Max-the-manager. Oh the irony ;)</div>
</div>
</blockquote>
</div>
</blockquote>
heey! :)<br>
<blockquote
cite="mid:42FEEA91-1629-47D9-8547-98544D3D6CD7@hibernate.org"
type="cite">
<div>
<blockquote type="cite">
<div style="">
<div>logicalColumnName is the name by which a column should be
referred in metadata descriptors (like unique constraints, indexes
etc). I don't think a user needs to use the logical mapping in HBM
files (the metadata structure don't require it contrary to annotations).</div>
<div>Anyway, the logical name should never appear in a physical
column name, so HbmBinder #fail.</div>
<div><a moz-do-not-send="true"
href="http://opensource.atlassian.com/projects/hibernate/browse/HHH-4077">http://opensource.atlassian.com/projects/hibernate/browse/HHH-4077</a></div>
<div><br>
</div>
<div>I've attached a patch and applied it to trunk. It probably
needs a quick test on your side and can be retrofitted to older
versions.</div>
</div>
</blockquote>
</div>
</blockquote>
Doesn't this change the behavior radically ? ...and how should our
validator know which sequence of calls it should use ...i hate bugs ;0)<br>
<br>
Looking in fisheye this change were done almost 4 years ago... <a
href="http://fisheye.jboss.org/changelog/Hibernate?cs=8918">http://fisheye.jboss.org/changelog/Hibernate?cs=8918</a><br>
for <a
href="http://opensource.atlassian.com/projects/hibernate/browse/ANN-176">http://opensource.atlassian.com/projects/hibernate/browse/ANN-176</a>
where it seems to be done very deliberately ?<br>
<br>
are you sure this is a proper change ? <br>
<a href="http://fisheye.jboss.org/changelog/Hibernate?cs=8918"></a>
<blockquote
cite="mid:42FEEA91-1629-47D9-8547-98544D3D6CD7@hibernate.org"
type="cite">
<div>
<blockquote type="cite">
<div style="">
<div>FTR</div>
Hibernate Annotations uses a different naming strategy than core for
backward compatibility reasons.
<div>JPA defaults are not Hibernate Core defaults</div>
<div><a moz-do-not-send="true"
href="http://anonsvn.jboss.org/repos/hibernate/core/trunk/annotations/src/main/java/org/hibernate/cfg/EJB3NamingStrategy.java">http://anonsvn.jboss.org/repos/hibernate/core/trunk/annotations/src/main/java/org/hibernate/cfg/EJB3NamingStrategy.java</a></div>
</div>
</blockquote>
</div>
</blockquote>
Yes, but that we will just pick up automatically since it does not
change the sequence of calls done to the namingstrategy.<br>
<br>
Anyway, for now we'll just focus on the JPA behavior since that is the
most relevant for JPA Project validation at least ;)<br>
<br>
/max
</body>
</html>