I didnt started the project I am only maintaining it. I would love to donate this code since this is so dangerous. I wont think about the money this might have cost to find these bugs in a live system. Especially if the database gots mixed up over these.
But you are right annotating actions and pages might be a better way anyhow. But my standpoint is that the framework should protect me and my coworker for doing such harmful stuff. I will look into the code again and commit / provide some code to the jira. Maybe one can pick it up. It also supports hibernates read only transactions to allow the utilization of slave db nodes which is currently not supported by tapestry. 2013/8/30 Lance Java <lance.j...@googlemail.com> > 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? >
