Return-Path: Delivered-To: apmail-tapestry-users-archive@www.apache.org Received: (qmail 71510 invoked from network); 2 Mar 2011 05:18:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Mar 2011 05:18:58 -0000 Received: (qmail 40980 invoked by uid 500); 2 Mar 2011 05:18:58 -0000 Delivered-To: apmail-tapestry-users-archive@tapestry.apache.org Received: (qmail 40647 invoked by uid 500); 2 Mar 2011 05:18:55 -0000 Mailing-List: contact users-help@tapestry.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tapestry users" Delivered-To: mailing list users@tapestry.apache.org Received: (qmail 40633 invoked by uid 99); 2 Mar 2011 05:18:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Mar 2011 05:18:54 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of hlship@gmail.com designates 209.85.210.180 as permitted sender) Received: from [209.85.210.180] (HELO mail-iy0-f180.google.com) (209.85.210.180) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Mar 2011 05:18:49 +0000 Received: by iyf40 with SMTP id 40so5802173iyf.11 for ; Tue, 01 Mar 2011 21:18:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=RUeT0P1qp7kXsT/FD4C/fsHo3TzKnQegIHXD7eDvYjQ=; b=qFik38SP54bTe+URtEU35h6mIK0me6uizEE0MgnoGXp6ZqGQ8Lvx/wJyHpwDemo1dz BdtfMEJgg64e/QCOC1yzLxBygCTEzJtHLcFUGTSwfg1L6/gXNde7Y7XwReldJEKANM6R 54PSmxenhopBZDiDLx3De8d8fSmZw9TGRAJvE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=xjV9egMgSuJ9D7kWo4TIEKszm9KET9vpiQTaHd/R5VHw17b6HCKqeTJWb9bFIc3uQL r3P8+Ip7e8ZfPLrYjVSwlhg04YmIT9Zfg+5McamAd/qldPe+b+HxUhmJbXoMpi/cjN8r 4YddO1AsiL8DR+1OcQMJz7m6bqnK9GZptQxRQ= MIME-Version: 1.0 Received: by 10.42.1.199 with SMTP id 7mr498260ich.490.1299043109097; Tue, 01 Mar 2011 21:18:29 -0800 (PST) Received: by 10.42.139.1 with HTTP; Tue, 1 Mar 2011 21:18:29 -0800 (PST) In-Reply-To: <1299033042808-3405994.post@n5.nabble.com> References: <1299033042808-3405994.post@n5.nabble.com> Date: Tue, 1 Mar 2011 21:18:29 -0800 Message-ID: Subject: Re: Tapestry 5.2 - Request data shared in different client browser From: Howard Lewis Ship To: Tapestry users Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Yes, this is a subtle offshoot of the 5.2 changes. What you've done is identify that single instance of LoginVO as the default value for the loginVo field. In 5.1, your bug was that different clients who accessed the same page instance sequentially would see data bleed from one request to the next. In 5.2, your bug is that all users see the data bleed, because there's only one instance of your page, and so, only one instance of LoginVO. Don't use objects with mutable state as the default values for fields. It causes data to bleed between requests and clients. On Tue, Mar 1, 2011 at 6:30 PM, Dany wrote: > Hi, > > I am developing in tapestry 5.2. I have including pages and component but= i > noticed one problem: > > =A0 =A0 =A0 =A0@Property > =A0 =A0 =A0 =A0Private LoginVo loginVo; > > =A0 =A0 =A0 =A0@Log > =A0 =A0 =A0 =A0@PageLoaded > =A0 =A0 =A0 =A0void pageLoaded() > =A0 =A0 =A0 =A0{ > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0loginVo =3Dnew LoginVo(); > =A0 =A0 =A0 =A0} > > t:value=3D"loginVo.username" t:validate=3D"required"/> > > t:value=3D"loginVo.password" t:validate=3D"required"/> > > if we include this value object in the page and initializes in the > PageLoaded =A0the page will be render, providing a response to the browse= r. > > we fille up this values with any value for example xxx and yyy and press > submit.Then if we open a =A0new browser instance and we call to this page= it > is appear the form with the fields values xxx and yyy even. I test this > behabiour in diferent PC browser with the same result. > > In tapestry 5.2 we have a sigleton page and not pooled pages but the sess= ion > can not be share with the rest of user i try to use ResetPaged but it > doesn=B4t work finally and setup tapestry for the used of pooled pages. > > I check it the same example in tapestry 5.1.5 and this it work fine. If y= ou > call with diferent browser intances the fields are null even if you > initializes the values in a instance browser. > > Is this a bug in tapestry 5.2 or has to be used in a diferent way?? > In which method i have to initializes the POJO=B4s attribubes? > > Any help will be welcome. Thanks in advance. > > > -- > View this message in context: http://tapestry.1045711.n5.nabble.com/Tapes= try-5-2-Request-data-shared-in-different-client-browser-tp3405994p3405994.h= tml > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org > For additional commands, e-mail: users-help@tapestry.apache.org > > --=20 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-unsubscribe@tapestry.apache.org For additional commands, e-mail: users-help@tapestry.apache.org