(via Transaction.wasRolledback()).
I'm not sure if I should file a new JIRA or re-open
https://issues.apache.org/jira/browse/TAPESTRY-2454. Please advise.
thanks,
B
--
View this message in context:
http://www.nabble.com/-T5--tapestry-hibernate-and-transactions-tp17767677p19300096.html
Sent
Hibernate expert, but I think maybe
hsm.commit() should get again the transaction with session.getTransaction
after it commits the current transaction.
Regards.
--
View this message in context:
http://www.nabble.com/-T5--tapestry-hibernate-and-transactions-tp17767677p17767677.html
Sent from
get again the transaction with session.getTransaction
after it commits the current transaction.
Regards.
--
View this message in context:
http://www.nabble.com/-T5--tapestry-hibernate-and-transactions-tp17767677p17767677.html
Sent from the Tapestry - User mailing list archive at Nabble.com
.
I'm not neither a Tapestry nor Hibernate expert, but I think maybe
hsm.commit() should get again the transaction with
session.getTransaction
after it commits the current transaction.
Regards.
--
View this message in context:
http://www.nabble.com/-T5--tapestry-hibernate-and-transactions
on the database) all works perfectly.
I'm not neither a Tapestry nor Hibernate expert, but I think maybe
hsm.commit() should get again the transaction with session.getTransaction
after it commits the current transaction.
Regards.
--
View this message in context:
http://www.nabble.com/-T5--tapestry