In mapping XML, at the time of resolving a property name to a field or getter/setter method Hibernate does not yet know the type. So if the class defines multiple potential matches based solely on name, Hibernate will not be able to adequately decide between them. At the moment it just picks the first one it sees. Unfortunately different JVMs (even different versions from the same VM vendor) returns the methods in different orders.
So if we (for example) match a property named active to a getter method named isActive, check that there is also not a method named getActive of differing type. If we do find such a getActive method, throw the MappingException.
It is the same bug as HHH-10093, but for version 5.0.2. There you can find more information.
Under Java 6 this does not happen, the exception is thrown when I use Java 8 (currently update 60).
After I do a simple session.get(Class, Serializable) , when I call Transaction.commit():
It reads all the properties in the xml order without problems. After it reads the last property, the call with the issue is made.
So, in DefaultFlushEntityEventListener line 135
The issue appear on line 142
The owner object is of class Boolean with value false, instead of being an Articulo class.