I'm not sure why you'd expect Tapestry to find a session that it didn't create and commit a transaction that it doesn't know about?
On Wed, Nov 28, 2012 at 1:07 PM, Pillar <sotodel...@hotmail.com> wrote: > It is in a Controller. If it was in DAO Layer, do I still use the @Inject > for > a session or get it from HibernateUtils style class? > > Now regardless of if I get the Transaction from the Session I'm given from > the SessionFactory, shouldn't Tapestry be finding the same Transaction and > committing it? > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/CommitAfter-not-committing-my-transaction-tp5718364p5718367.html > Sent from the Tapestry - User 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 > >
