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
I've put another round of performance enhancements into Tapestry
5.3.4. This will be most effective in applications that make use of
Session State Objects.
This preview release has been made available as Tapestry 5.3.4-rc-3.
If you are in a position too, please pull it down and give it a whirl!
What version of Tapestry are you using?
On Fri, May 25, 2012 at 3:13 AM, Arming, Sebastian
wrote:
> Hi
>
> I tried to @Inject a Logger into a service (a tapestry-resteasy resource if
> that matters) and got an exception:
> oejs.ServletHandler:/intern/
> java.lang.RuntimeException: Exception con
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
