Here is the output from build-time enhancer. Buildfile: build.xml
enhance: [openjpac] 463 UserAdminTestCase WARN [main] openjpa.MetaData - No setter was found for method new in type com.example.model.impl.UserModelBaseImpl while searching for persistent properties. This method will be ignored. If you intended for this to be persistent, please add a corresponding setter, or switch to field access for this type hierarchy. [openjpac] 519 UserAdminTestCase WARN [main] openjpa.MetaData - Found duplicate metadata or mapping for "class com.example.model.impl.UserModelBaseImpl". Ignoring. [openjpac] 523 UserAdminTestCase WARN [main] openjpa.MetaData - Found duplicate metadata or mapping for "class com.example.model.impl.UserModelImpl". Ignoring. [openjpac] 582 UserAdminTestCase WARN [main] openjpa.Enhance - Detected the following possible violations of the restrictions placed on property access persistent types: [openjpac] "com.example.model.impl.UserModelBaseImpl" uses property access, but its field "id" is accessed directly in method "isNew" defined in "com.example.model.impl.UserModelBaseImpl". [openjpac] "com.example.model.impl.UserModelBaseImpl" uses property access, but its field "active" is accessed directly in method "isActive" defined in "com.example.model.impl.UserModelBaseImpl". BUILD SUCCESSFUL Total time: 1 second I am using spring and load-time weaver of spring on tomcat at runtime. That works fine with EclipseLink though. -- View this message in context: http://n2.nabble.com/overriding-accesors-in-entity-need-tranisent-declaration-tp3363414p3396927.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
