Seperation of concerns rules the approach below out, however you can always create a top level facade layer between your DAOs and pages/components to resolve this. Your DAO classes can then be trivial CRUD implementations.
John ----- Original Message ----- From: Lance Java To: Tapestry users Sent: Friday, August 30, 2013 11:47 AM Subject: Re: Using Hibernate Session outside of @CommitAfter. Bugs I saw in our project I never annotate my services or dao's with @CommitAfter and only annotate the actions in my pages / components. Is there a reason why you can't use this approach?
