I tried using eclipselink with tapestry-jpa and i had the same errors as you with jetty.I though that the problem was that i was not doing weaving so i stopped there and revert back to hibernate.If what you are saying is correct (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) then it should work.Btw if you find a solution please post it on the list
On Thu, Oct 20, 2011 at 6:51 PM, jesse <jessegr...@hotmail.com> wrote: > 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 > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
