[TAPESTRY-2247] Transactions should roll back, not commit, at the end of each request

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.10
• Fix Version/s: 5.0.12
• Component/s: tapestry-hibernate
• Assignee: Howard Lewis Ship
• Reporter: Dan Adams
• Created: 08/Mar/08 23:59
• Updated: 13/Apr/08 22:30
• Resolved: 05/Apr/08 15:05

Description

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.