Hi there,
after my struggle with the current @CommitAfter implementation and the
transaction handling I was able to fix it for the actual project I am
working on. I found several places where my coworker and introduced bugs
because of the current (flawed) implementation of @CommitAfter.
(For
I also now have true read only transaction that set the underlying jdbc
connection to read only and FlushMode.Never for the session. And yes the
read only transactions are also committed so you do not spam your database
logs with rollback information.
2013/8/27 Martin Kersten
> Hi there,
>
>
>
On Sun, May 27, 2012 at 7:18 PM, Fight Ice wrote:
> Thx, I use HibernateSessionSource.create(). Is this thread safe?
Are sessions thread safe? No.
Kalle
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additi
Thx, I use HibernateSessionSource.create(). Is this thread safe?
On Sun, May 27, 2012 at 2:33 AM, Fight Ice wrote:
> java code:
> Transaction ts=session.beginTransaction();
> Criteria criteria=session.createCriteria(Item.class);
> criteria.add(Restrictions.idEq(product.getItem().getId()));
> criteria.setLockMode(LockMode.PESSIMISTIC_WRITE);
> Item item=(Item)cr
On Sun, 27 May 2012 06:33:09 -0300, Fight Ice wrote:
java code:
Transaction ts=session.beginTransaction();
Criteria criteria=session.createCriteria(Item.class);
criteria.add(Restrictions.idEq(product.getItem().getId()));
criteria.setLockMode(LockMode.PESSIMISTIC_WRITE);
Item item=(Item)criter
java code:
Transaction ts=session.beginTransaction();
Criteria criteria=session.createCriteria(Item.class);
criteria.add(Restrictions.idEq(product.getItem().getId()));
criteria.setLockMode(LockMode.PESSIMISTIC_WRITE);
Item item=(Item)criteria.list().get(0);
...
ts.commit();
...
Transaction tc=ses
")
.setProperty("hibernate.hbm2ddl.auto", "update") ;
Any thoughts what might be the reason for the described behavior?
Stephan
-
--
http://www.caimito.net - Caimito One Team - Agile Collaboration and Planning
tool
http://www.stephan-schwab.com - Personal blog
http://code.
is one successfull @CommitAfter and one failed.
>
> Is the correct approach to wrap multiple service calls in to one and
> annotate only this?
>
> -99
>
--
View this message in context:
http://www.nabble.com/T5---Hibernate---Transacti
to wrap multiple service calls in to one and
> annotate only this?
>
> -99
>
--
View this message in context:
http://www.nabble.com/T5---Hibernate---Transaction-confusion-tp18826235p18826695.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---
and one failed.
Is the correct approach to wrap multiple service calls in to one and
annotate only this?
-99
--
View this message in context:
http://www.nabble.com/T5---Hibernate---Transaction-confusion-tp18826235p18826235.html
Sent from the Tapestry - User mailing list archiv
t:
http://www.nabble.com/tapestry-hibernate-Transaction-not-successfully-started-tp18550915p18550915.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For ad
12 matches
Mail list logo