[ http://issues.apache.org/jira/browse/OPENJPA-41?page=comments#action_12440115 ] Costin Leau commented on OPENJPA-41: ------------------------------------
For some reason the JIRA comment was not email to me. Anyway, using the 'fixed' orm.xml seemed to do the trick. I've got some errors now about the HSQLDB columns not found but I think that's related to the dialect and the ddl used. TopLink seems to run fine with both property tags apparently... Consider the issue fixed for now. Thanks! > transforming classes doesn't work > --------------------------------- > > Key: OPENJPA-41 > URL: http://issues.apache.org/jira/browse/OPENJPA-41 > Project: OpenJPA > Issue Type: Bug > Components: jpa > Environment: WinXP, Tomcat 5.5.17, Spring 2.0-RC4 > Reporter: Costin Leau > Assigned To: Marc Prud'hommeaux > Attachments: petclinic.zip, spring-tomcat-weaver.jar, > stacktrace-2.txt, stacktrace.txt > > > I've tried several versions of OpenJPA including the most recent one(svn > 4409856) to run Spring's Petclinic with class level LoadTimeWeaver on OpenJPA. > I have attached the stacktrace that I get. The same example works fine with > Toplink. > I have attached petclinic w/o some of the libs to gain space; basically add > the OpenJPA libs and deploy the war into Tomcat. Note that you'll also have > to place spring-tomcat-weaver.jar under Tomcat's server/lib (this should be > enough - if you have problems let me know or take a look at the Spring > reference documentation). > When the webapp starts, the exception pops up. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
