PERTHREAD values are discarded at the end of each request On Wed, Oct 19, 2011 at 6:56 AM, Keio Kraaner <k.kraa...@gmail.com> wrote: > Hi > > Shouldn't AjaxFormUpdateControllerImpl.cleanupAfterPartialZoneRender() > assign null to formComponentId after it has checked it is not null? > As the service's scope is PERTHREAD it means that at the moment the > following scenario is possible: > - thread A processes an Ajax request, finds out that the request has > parameters t:formid and t:formcomponentid defined and > initializes AjaxFormUpdateController service with these. > - after a while thread A processes another Ajax request, the request does > not have the abovementioned parameters defined, but AjaxFormUpdateController > service (for thread A) is still configured with old values which can cause > problems. > > Regards > Keio Kraaner >
-- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
