Hi Thiago, I'm talking about the hibernate session - I'm injecting it into the constructor of Service B at bind time. I thought Tapestry would treat the service as a thread safe singleton and control access to method calls on it accordingly? Am I getting confused on that?
Regards, Jim. -----Original Message----- From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com] Sent: 21 July 2010 17:38 To: Tapestry users Subject: Re: non thread safe access to session Are you talking about Tapestry sessions or Hibernate sessions? Hibernate sessions should never be used at the same time by more than one thread. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informa��o Ltda. http://www.arsmachina.com.br --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
