Folks,

There was too much data to re-type. I put it in a JIRA for all to see.

http://opensource.atlassian.com/project ... se/ANN-611

All I am doing is instrumenting/leveraging/querying the internals of the annotation at bootstrap time...

And I am seeing ManyToOneType being binded/coupled with OneToOneType

Can I get some feedback on this?

Much appreciated.

This post offered no relief.

http://forum.hibernate.org/viewtopic.php?t=962091

Seems I am referencing a non-pk column.

Any help is appreciated.

So is this by design?.. that hibernate does not want developers to be navigating across classes like this?

Gavin or Christian, can you offer me a solution please?

Thank You

// http://forums.hibernate.org/viewtopic.p ... 190cfc4e60
// Danger Will Robinson... this does not support multiple
// class references across the OneToOne relationship, Dr. Hack
Class returnType = readMethod.getReturnType();
String ognlUsableProperty = "";
for ( int i = 0; i < returnType.getDeclaredMethods().length; i++ ) {
if ( returnType.getDeclaredMethods()[i].getReturnType().equals(propertyField.getDeclaringClass()) ) {
Method theProperty = returnType.getDeclaredMethods()[i];
ognlUsableProperty = org.trails.component.Utils.unCamelCase(theProperty.getName()).substring(3); // strips preceding 'get'
break;
}
}