[
https://issues.apache.org/jira/browse/TAPESTRY-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Howard M. Lewis Ship closed TAPESTRY-2247.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.12
Ultimately, we need to add some form of @Commit annotation as well, so that
user code doesn't have to directly deal with the HibernateSessionManager.
> Transactions should roll back, not commit, at the end of each request
> ---------------------------------------------------------------------
>
> Key: TAPESTRY-2247
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2247
> Project: Tapestry
> Issue Type: Task
> Components: tapestry-hibernate
> Affects Versions: 5.0.10
> Reporter: Dan Adams
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.12
>
>
> On thread cleanup, the Session should be flushed not committed. If people
> want to commit changes they should explicitly do so but having the
> transaction committed automatically can lead to some very mysterious changing
> of the data. In my experience, having the transaction committed automatically
> does more harm than good.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
