I really appreciate your quick response, and thanks for trying to help! Yes, my app uses weaving - otherwise it wouldn't work with lazy loaded entities. Eclipselink uses weaving by default. When you run your app in a j2ee container (like tomcat and jetty, both of which I'm using) you don't need to do anything for weaving to work. You don't need to use a plugin in your pom to do the weaving at build time.
It's totally possible that I'm missing something here but this app works fine with tapestry 5.2.6 and tynamo's implementation of tapestry-jpa, which is why I'm wondering if there is a bug in the new tapestry-jpa module. -- View this message in context: http://tapestry-users.832.n2.nabble.com/Problems-using-JPA-with-5-3-tp6898469p6913446.html Sent from the Tapestry Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
