I agree that it is not a common issue, but I've been struggling with this for more than a year. I even had to add a restriction in my software in order to show an error message to the user if a greater version of Java 6 was used.
I only found one mention of this in Stackoverflow, so again it is not a common issue.
Just a thought, what if you add a check before returning a value in getGetterOrNull or findGetterMethod or whatever you think is best. Since you look for methodName.startsWith( "get" ) or methodName.startsWith( "is" ) }}, if {{getDeclaredMethods() has the strings "get" + propertyName and "is" + propertyName then throw a MappingException telling the developer the mistake that has done. This simple check will be very useful to avoid headaches for people like me
Regarding your options, since you are a Hibernate guru I would like to know if annotations are faster and less error prone than XML mapping. I ask you this because of this issue, but also because I see a lot of weekly downloads for version 5 and only me and one other guy asked about the performance issue on startup caused by XML mapping.
|