On Mon, Apr 30, 2012 at 11:32 AM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote:
> > One per thread (maybe zero, if it ends up not being used in a given >> thread). If you take a look at them in a debugger, the injected service >> object may look like there's a single shared instance, but actually it acts >> as a proxy and delegates method calls to the appropriate service instance >> for that thread. > > I was trying to explain the symptoms with a colleague and all the sudden I learnt where the problem was, and of course, It was not tapestry. Sorry about the noise Regards, Manuel.
