From usersboothjason@example.com Sat Dec 01 02:34:42 2007 Return-Path: <usersboothjason@example.com> Delivered-To: boothjason@example.com Received: (qmail 990 invoked from network); 1 Dec 2007 02:34:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Dec 2007 02:34:42 -0000 Received: (qmail 13409 invoked by uid 500); 1 Dec 2007 02:34:23 -0000 Delivered-To: boothjason@example.com Received: (qmail 13396 invoked by uid 500); 1 Dec 2007 02:34:23 -0000 Mailing-List: contact boothjason@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:boothjason@example.com> List-Unsubscribe: <mailto:boothjason@example.com> List-Post: <mailto:boothjason@example.com> List-Id: <users.tapestry.apache.org> Reply-To: "Tapestry users" <boothjason@example.com> Delivered-To: mailing list boothjason@example.com Received: (qmail 13387 invoked by uid 99); 1 Dec 2007 02:34:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Nov 2007 18:34:23 -0800 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of boothjason@example.com does not designate 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO out1.smtp.messagingengine.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 02:34:03 +0000 Received: from compute1.internal (compute1.internal [83.161.120.155]) by out1.messagingengine.com (Postfix) with ESMTP id 118B557ECE for <boothjason@example.com>; Fri, 30 Nov 2007 21:34:06 -0500 (EST) Received: from heartbeat2.messagingengine.com ([83.161.120.155]) by compute1.internal (MEProxy); Fri, 30 Nov 2007 21:34:06 -0500 X-Sasl-enc: u24+uYl/urMw3gIyd5dqc5ftWrVQvi6y9dYsI6/UiBuU 1196476445 Received: from [83.161.120.155] (unknown [83.161.120.155]) by mail.messagingengine.com (Postfix) with ESMTP id C639823060 for <boothjason@example.com>; Fri, 30 Nov 2007 21:34:05 -0500 (EST) Message-ID: <boothjason@example.com> Date: Fri, 30 Nov 2007 18:34:04 -0800 From: Fernando Padilla <boothjason@example.com> User-Agent: Thunderbird 83.161.120.155 (X11/20071116) MIME-Version: 1.0 To: Tapestry users <boothjason@example.com> Subject: possible bug: onActivate/onDeactivate and ComponentActions Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org The bug we're seeing is that the page context is being set by an onActivate call, but it's never being cleaned up. So the next page render still has the old page context setup, and we don't have a chance to re-null it. normally while handling a page: onActivate setupRender ... cleanupRender We can absorb the context and cleanup anything that needs to be cleaned up within the "cleanupRender". But for ComponentActions, there is no such "cleanup" method available: onActivate onAction Proposed solution is really easy, just add an "onDeactivate" event. Allowing us to undo any page activation. ideas? --------------------------------------------------------------------- To unsubscribe, e-mail: boothjason@example.com For additional commands, e-mail: boothjason@example.com From usersboothjason@example.com Sat Dec 01 07:31:41 2007 Return-Path: <usersboothjason@example.com> Delivered-To: boothjason@example.com Received: (qmail 73269 invoked from network); 1 Dec 2007 07:31:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Dec 2007 07:31:41 -0000 Received: (qmail 16967 invoked by uid 500); 1 Dec 2007 07:31:22 -0000 Delivered-To: boothjason@example.com Received: (qmail 16948 invoked by uid 500); 1 Dec 2007 07:31:21 -0000 Mailing-List: contact boothjason@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:boothjason@example.com> List-Unsubscribe: <mailto:boothjason@example.com> List-Post: <mailto:boothjason@example.com> List-Id: <users.tapestry.apache.org> Reply-To: "Tapestry users" <boothjason@example.com> Delivered-To: mailing list boothjason@example.com Received: (qmail 16939 invoked by uid 99); 1 Dec 2007 07:31:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Nov 2007 23:31:21 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of boothjason@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO wr-out-0506.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 07:31:02 +0000 Received: by wr-out-0506.google.com with SMTP id c55so2836543wra for <boothjason@example.com>; Fri, 30 Nov 2007 23:31:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=yFqlWBhgGLl4sUiYL7KmI1DZeBIG6RuGdvxZzeEfwVc=; b=gmgHoZeyKucdrrRYcYSiP2pkpZLuxYhSn9G5LjmD1Dr4+sheVjJpc642WhT8jdXAD4NGLQM5wonJcb9aw3Ob95TBUMU98LaR9nGUcVTcNGtTKAz0OxEQxbWdgcykK+OENCWLXQDBTkVn+AgCjZRt7dR4vqQlRCklOlW2DjsKIg0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=j/fYKmEkCQApi9wjwnr8frxSQU4Y2XjBWdVNwGyallawb4vMd/JkHmh99SZXKqdFCWSZAAUzfDnEzJT/MKReF3X2fXKRAwX4ZygbinmZ/h5NMOd6zDYuNCzu8EENYiw7JoFbAcMMnTvZuHqMOGuSvvphZxC3WFHgK7thk5bmVe0= Received: by 83.161.120.155 with SMTP id u19mr331833wxu.1196494264111; Fri, 30 Nov 2007 23:31:04 -0800 (PST) Received: by 83.161.120.155 with HTTP; Fri, 30 Nov 2007 23:31:04 -0800 (PST) Message-ID: <boothjason@example.com> Date: Fri, 30 Nov 2007 23:31:04 -0800 From: "Howard Lewis Ship" <boothjason@example.com> To: "Tapestry users" <boothjason@example.com> Subject: Re: possible bug: onActivate/onDeactivate and ComponentActions In-Reply-To: <boothjason@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <boothjason@example.com> X-Virus-Checked: Checked by ClamAV on apache.org What possible state would you have to clean up? Assuming you are using proper instance variables (all private), then Tapestry already does end-of-request cleanup, resetting all your fields to correct default values (for those that are not set to fixed values via an injection). On Nov 30, 2007 6:34 PM, Fernando Padilla <boothjason@example.com> wrote: > The bug we're seeing is that the page context is being set by an > onActivate call, but it's never being cleaned up. So the next page > render still has the old page context setup, and we don't have a chance > to re-null it. > > > > normally while handling a page: > > onActivate > setupRender > ... > cleanupRender > > We can absorb the context and cleanup anything that needs to be cleaned > up within the "cleanupRender". But for ComponentActions, there is no > such "cleanup" method available: > > onActivate > onAction > > > > Proposed solution is really easy, just add an "onDeactivate" event. > Allowing us to undo any page activation. > > > ideas? > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: boothjason@example.com > For additional commands, e-mail: boothjason@example.com > > -- Howard M. Lewis Ship TWD Consulting, Inc. Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: boothjason@example.com For additional commands, e-mail: boothjason@example.com From usersboothjason@example.com Sat Dec 01 14:30:29 2007 Return-Path: <usersboothjason@example.com> Delivered-To: boothjason@example.com Received: (qmail 69039 invoked from network); 1 Dec 2007 14:30:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Dec 2007 14:30:29 -0000 Received: (qmail 21101 invoked by uid 500); 1 Dec 2007 14:30:11 -0000 Delivered-To: boothjason@example.com Received: (qmail 20495 invoked by uid 500); 1 Dec 2007 14:30:10 -0000 Mailing-List: contact boothjason@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:boothjason@example.com> List-Unsubscribe: <mailto:boothjason@example.com> List-Post: <mailto:boothjason@example.com> List-Id: <users.tapestry.apache.org> Reply-To: "Tapestry users" <boothjason@example.com> Delivered-To: mailing list boothjason@example.com Received: (qmail 20486 invoked by uid 99); 1 Dec 2007 14:30:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 06:30:10 -0800 X-ASF-Spam-Status: No, hits=-2.8 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO xsmtp1.ethz.ch) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 14:29:48 +0000 Received: from xfe0.d.ethz.ch ([83.161.120.155]) by xsmtp1.ethz.ch with Microsoft SMTPSVC(646)582-0504); Sat, 1 Dec 2007 15:29:49 +0100 Received: from [83.161.120.155] ([83.161.120.155]) by xfe0.d.ethz.ch over TLS secured channel with Microsoft SMTPSVC(646)582-0504); Sat, 1 Dec 2007 15:29:49 +0100 Mime-Version: 1.0 (Apple Message framework v752.3) Content-Transfer-Encoding: 7bit Message-Id: <boothjason@example.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: Tapestry users <boothjason@example.com> From: Kaspar Fischer <boothjason@example.com> Subject: =?WINDOWS-1252?Q?Single_OGNL_expression_evaluated_several_times_?= =?WINDOWS-1252?Q?=96=A0is_it_normal=3F?= Date: Sat, 1 Dec 2007 15:29:47 +0100 X-Mailer: Apple Mail (2.752.3) X-OriginalArrivalTime: 01 Dec 2007 14:29:49.0160 (UTC) FILETIME=[A0D25680:01C83426] X-Virus-Checked: Checked by ClamAV on apache.org Hi, My Page.html contains a single Tapestry component: <title><span jwcid="@Insert" value="ognl:title">Title</span></title> Why is my page's method getTitle() executed several times? 15:23:11,106 User:admin DEBUG [knowledgecenter.pages.NodePage] NodePage.pageBeginRender(). 15:23:11,188 User:admin DEBUG [knowledgecenter.pages.NodePage] NodePage.getTitle(). 15:23:11,204 User:admin DEBUG [knowledgecenter.pages.NodePage] NodePage.getTitle(). 15:23:11,244 User:admin DEBUG [knowledgecenter.pages.NodePage] NodePage.getTitle(). 15:23:11,377 User:admin DEBUG [knowledgecenter.pages.NodePage] NodePage.pageEndRender(). Is this normal or have I misconfigured Tapestry in some way? Kaspar --------------------------------------------------------------------- To unsubscribe, e-mail: boothjason@example.com For additional commands, e-mail: boothjason@example.com From usersboothjason@example.com Sat Dec 01 17:46:29 2007 Return-Path: <usersboothjason@example.com> Delivered-To: boothjason@example.com Received: (qmail 17012 invoked from network); 1 Dec 2007 17:46:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Dec 2007 17:46:29 -0000 Received: (qmail 20080 invoked by uid 500); 1 Dec 2007 17:46:13 -0000 Delivered-To: boothjason@example.com Received: (qmail 20062 invoked by uid 500); 1 Dec 2007 17:46:13 -0000 Mailing-List: contact boothjason@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:boothjason@example.com> List-Unsubscribe: <mailto:boothjason@example.com> List-Post: <mailto:boothjason@example.com> List-Id: <users.tapestry.apache.org> Reply-To: "Tapestry users" <boothjason@example.com> Delivered-To: mailing list boothjason@example.com Received: (qmail 20038 invoked by uid 99); 1 Dec 2007 17:46:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 09:46:12 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of boothjason@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO wa-out-1112.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 17:45:53 +0000 Received: by wa-out-1112.google.com with SMTP id j37so3783468waf for <boothjason@example.com>; Sat, 01 Dec 2007 09:45:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=TKMw8oZtU/HU9tHVKMs6SPWdKak4vX98WsOj4k9UoZ8=; b=skDDosYWAjqeGEREhz0URAasuZJcQ8IqP1blxvHcWqtoB/GGG6ThpJvdFcmdJXjbNEFrKKwaxCtwDc5FJbuKJDGGW2I7Wxg369lOILXhRSb5pffhiVZ3b215AgqbSa6ohM3khJ2ogK/I5sZ6QtUhCLVMmfoi2G64K5jC0/F0XvQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:message-id:date:from:to:subject:mime-version:content-type; b=YAqT6c7UniSwD50qjPmvKLXnZNGZ+hYTmH5av08zfW+FBj8+BEjipD8Hdn71dtZNvY0pZh77KMTcmSnXTads6xuSKXy+p5fU8NF46rDLGRSQX9toPTWAXBS+hi6LIjFNXl2nE3oNO2uYoRm3SDKIbYO4RSvtthahjBT3WsczRO8= Received: by 83.161.120.155 with SMTP id y1mr1344782waa.1196531156207; Sat, 01 Dec 2007 09:45:56 -0800 (PST) Received: by 83.161.120.155 with HTTP; Sat, 1 Dec 2007 09:45:56 -0800 (PST) Message-ID: <boothjason@example.com> Date: Sat, 1 Dec 2007 09:45:56 -0800 From: "Kalle Korhonen" <boothjason@example.com> To: "Tapestry users" <boothjason@example.com> Subject: T4: From the client side, how do you programmatically update a component? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4576_2353569.1196531156203" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_4576_2353569.1196531156203 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I have a use case where I need to "click on" a directllink to updatecomponents with async=true or do an equivalent action in Javascript. I know I can do tapestry.bind('<span boothjason@example.com.../>') and it makes some sense, but looks rather ugly. Any cleaner way to accomplish this? Kalle ------=_Part_4576_2353569.1196531156203-- From usersboothjason@example.com Sat Dec 01 19:18:16 2007 Return-Path: <usersboothjason@example.com> Delivered-To: boothjason@example.com Received: (qmail 37005 invoked from network); 1 Dec 2007 19:18:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Dec 2007 19:18:16 -0000 Received: (qmail 67028 invoked by uid 500); 1 Dec 2007 19:18:01 -0000 Delivered-To: boothjason@example.com Received: (qmail 67010 invoked by uid 500); 1 Dec 2007 19:18:01 -0000 Mailing-List: contact boothjason@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:boothjason@example.com> List-Unsubscribe: <mailto:boothjason@example.com> List-Post: <mailto:boothjason@example.com> List-Id: <users.tapestry.apache.org> Reply-To: "Tapestry users" <boothjason@example.com> Delivered-To: mailing list boothjason@example.com Received: (qmail 67000 invoked by uid 99); 1 Dec 2007 19:18:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 11:18:01 -0800 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of boothjason@example.com does not designate 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO out1.smtp.messagingengine.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 19:17:40 +0000 Received: from compute1.internal (compute1.internal [83.161.120.155]) by out1.messagingengine.com (Postfix) with ESMTP id 0D2BD57B56 for <boothjason@example.com>; Sat, 1 Dec 2007 14:17:43 -0500 (EST) Received: from heartbeat2.messagingengine.com ([83.161.120.155]) by compute1.internal (MEProxy); Sat, 01 Dec 2007 14:17:43 -0500 X-Sasl-enc: cHVj5ZHR7AMA/8TM1S6tFKlzwuDO4Vk6wiT7Wn1mKwrf 1196536662 Received: from 141.sub-75-208-8.myvzw.com (141.sub-75-208-8.myvzw.com [83.161.120.155]) by mail.messagingengine.com (Postfix) with ESMTP id 2DF6A2594B for <boothjason@example.com>; Sat, 1 Dec 2007 14:17:41 -0500 (EST) Message-ID: <boothjason@example.com> Date: Sat, 01 Dec 2007 11:17:39 -0800 From: Fernando Padilla <boothjason@example.com> User-Agent: Thunderbird 83.161.120.155 (Macintosh/20071031) MIME-Version: 1.0 To: Tapestry users <boothjason@example.com> Subject: Re: possible bug: onActivate/onDeactivate and ComponentActions References: <boothjason@example.com> <boothjason@example.com> In-Reply-To: <boothjason@example.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Yeah, they were public. Making all my variables private is one of those things I do without thinking, and I forgot to check that in this case. Funny. I don't remember reading about tapestry setting all private variables to null (or their default values) in the docs. Maybe I skimmed that part of the docs when I read them a while back. My apologies, setting them to private and having Tapestry set them to null should take care of it then. Howard Lewis Ship wrote: > What possible state would you have to clean up? > > Assuming you are using proper instance variables (all private), then > Tapestry already does end-of-request cleanup, resetting all your > fields to correct default values (for those that are not set to fixed > values via an injection). > > On Nov 30, 2007 6:34 PM, Fernando Padilla <boothjason@example.com> wrote: >> The bug we're seeing is that the page context is being set by an >> onActivate call, but it's never being cleaned up. So the next page >> render still has the old page context setup, and we don't have a chance >> to re-null it. >> >> >> >> normally while handling a page: >> >> onActivate >> setupRender >> ... >> cleanupRender >> >> We can absorb the context and cleanup anything that needs to be cleaned >> up within the "cleanupRender". But for ComponentActions, there is no >> such "cleanup" method available: >> >> onActivate >> onAction >> >> >> >> Proposed solution is really easy, just add an "onDeactivate" event. >> Allowing us to undo any page activation. >> >> >> ideas? >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: boothjason@example.com >> For additional commands, e-mail: boothjason@example.com >> >> > > > --------------------------------------------------------------------- To unsubscribe, e-mail: boothjason@example.com For additional commands, e-mail: boothjason@example.com From usersboothjason@example.com Sat Dec 01 19:54:48 2007 Return-Path: <usersboothjason@example.com> Delivered-To: boothjason@example.com Received: (qmail 43040 invoked from network); 1 Dec 2007 19:54:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Dec 2007 19:54:47 -0000 Received: (qmail 91633 invoked by uid 500); 1 Dec 2007 19:54:28 -0000 Delivered-To: boothjason@example.com Received: (qmail 91435 invoked by uid 500); 1 Dec 2007 19:54:27 -0000 Mailing-List: contact boothjason@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:boothjason@example.com> List-Unsubscribe: <mailto:boothjason@example.com> List-Post: <mailto:boothjason@example.com> List-Id: <users.tapestry.apache.org> Reply-To: "Tapestry users" <boothjason@example.com> Delivered-To: mailing list boothjason@example.com Received: (qmail 91426 invoked by uid 99); 1 Dec 2007 19:54:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 11:54:27 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of boothjason@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO hs-out-2122.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 19:54:08 +0000 Received: by hs-out-2122.google.com with SMTP id k27so175249hsc for <boothjason@example.com>; Sat, 01 Dec 2007 11:54:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=+kjlY7rM7wNMiXmGBVyHkPYez5cKwp2/mKhXCq70IDo=; b=ELXxHqZom9V/TCFkSjR3sac3YJ3YGIxnBIU7PsMMTw2Lcsk4Y+AN5rftiQhO3k+o4UgaP4zaS+GovZ9A+6opl7oBTn9V0Q8OjucNt9bld7zGZoBFhVLiVrLkzE7PM5ny5jcdGZ3iZ0+qX9AFd6a7GLiJ4nAWMT6qiluw1s2yeZA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WDGTi2ZqZ8XskbgtcOXzwV7zxTgpZprVAiL6qRs3JiajpKfUNdRESttCFqgZJirwSDjoIOkmI95QFtrabim0aeL3AzjPLBSaqji/m8q9uBdGoy3z2cVIXFBUGwh4G0hyOF4cqt7JUJ1mC9pnn85k3DSb9AlWmgWq/77hZqLjmIA= Received: by 83.161.120.155 with SMTP id 10mr1344905wxu.1196538848829; Sat, 01 Dec 2007 11:54:08 -0800 (PST) Received: by 83.161.120.155 with HTTP; Sat, 1 Dec 2007 11:54:08 -0800 (PST) Message-ID: <boothjason@example.com> Date: Sat, 1 Dec 2007 11:54:08 -0800 From: "Howard Lewis Ship" <boothjason@example.com> To: "Tapestry users" <boothjason@example.com> Subject: Re: possible bug: onActivate/onDeactivate and ComponentActions In-Reply-To: <boothjason@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <boothjason@example.com> <boothjason@example.com> <boothjason@example.com> X-Virus-Checked: Checked by ClamAV on apache.org Tapestry generates warnings about any non-private fields it finds in a component class, so you might want to keep an eye on the console as well. Sometimes I think console warnings are useless as no one ever seems to see them, only by being "in your face" with a hard exception can you catch the developers' attention. On Dec 1, 2007 11:17 AM, Fernando Padilla <boothjason@example.com> wrote: > Yeah, they were public. Making all my variables private is one of those > things I do without thinking, and I forgot to check that in this case. > > Funny. I don't remember reading about tapestry setting all private > variables to null (or their default values) in the docs. Maybe I > skimmed that part of the docs when I read them a while back. > > My apologies, setting them to private and having Tapestry set them to > null should take care of it then. > > > > Howard Lewis Ship wrote: > > What possible state would you have to clean up? > > > > Assuming you are using proper instance variables (all private), then > > Tapestry already does end-of-request cleanup, resetting all your > > fields to correct default values (for those that are not set to fixed > > values via an injection). > > > > On Nov 30, 2007 6:34 PM, Fernando Padilla <boothjason@example.com> wrote: > >> The bug we're seeing is that the page context is being set by an > >> onActivate call, but it's never being cleaned up. So the next page > >> render still has the old page context setup, and we don't have a chance > >> to re-null it. > >> > >> > >> > >> normally while handling a page: > >> > >> onActivate > >> setupRender > >> ... > >> cleanupRender > >> > >> We can absorb the context and cleanup anything that needs to be cleaned > >> up within the "cleanupRender". But for ComponentActions, there is no > >> such "cleanup" method available: > >> > >> onActivate > >> onAction > >> > >> > >> > >> Proposed solution is really easy, just add an "onDeactivate" event. > >> Allowing us to undo any page activation. > >> > >> > >> ideas? > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: boothjason@example.com > >> For additional commands, e-mail: boothjason@example.com > >> > >> > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: boothjason@example.com > For additional commands, e-mail: boothjason@example.com > > -- Howard M. Lewis Ship TWD Consulting, Inc. Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: boothjason@example.com For additional commands, e-mail: boothjason@example.com From usersboothjason@example.com Sat Dec 01 22:45:53 2007 Return-Path: <usersboothjason@example.com> Delivered-To: boothjason@example.com Received: (qmail 82812 invoked from network); 1 Dec 2007 22:45:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Dec 2007 22:45:53 -0000 Received: (qmail 72595 invoked by uid 500); 1 Dec 2007 22:45:39 -0000 Delivered-To: boothjason@example.com Received: (qmail 72582 invoked by uid 500); 1 Dec 2007 22:45:39 -0000 Mailing-List: contact boothjason@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:boothjason@example.com> List-Unsubscribe: <mailto:boothjason@example.com> List-Post: <mailto:boothjason@example.com> List-Id: <users.tapestry.apache.org> Reply-To: "Tapestry users" <boothjason@example.com> Delivered-To: mailing list boothjason@example.com Received: (qmail 72572 invoked by uid 99); 1 Dec 2007 22:45:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 14:45:39 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO uli.spielviel.de) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 22:45:41 +0000 Received: from uli.spielviel.de (localhost [83.161.120.155]) by uli.spielviel.de (Postfix) with ESMTP id AB0073C81 for <boothjason@example.com>; Sat, 1 Dec 2007 23:45:08 +0100 (CET) Received: from [83.161.120.155] (i59F7DBC1.versanet.de [83.161.120.155]) by uli.spielviel.de (Postfix) with ESMTP id 828983C80 for <boothjason@example.com>; Sat, 1 Dec 2007 23:45:08 +0100 (CET) Message-ID: <boothjason@example.com> Date: Sat, 01 Dec 2007 23:45:09 +0100 From: =?ISO-8859-15?Q?Ulrich_St=E4rk?= <boothjason@example.com> User-Agent: Thunderbird 83.161.120.155 (Windows/20071031) MIME-Version: 1.0 To: Tapestry users <boothjason@example.com> Subject: Re: T4: From the client side, how do you programmatically update a component? References: <boothjason@example.com> In-Reply-To: <boothjason@example.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-Virus-Checked: Checked by ClamAV on apache.org I can't follow you. You want a component to update itself asynchronously upon a user's click on a DirectLink? Why don't you just use DirectLink's updateComponents parameter with async="true"? Uli Kalle Korhonen schrieb: > I have a use case where I need to "click on" a directllink to > updatecomponents with async=true or do an equivalent action in Javascript. I > know I can do tapestry.bind('<span boothjason@example.com.../>') and it makes > some sense, but looks rather ugly. Any cleaner way to accomplish this? > > Kalle > --------------------------------------------------------------------- To unsubscribe, e-mail: boothjason@example.com For additional commands, e-mail: boothjason@example.com From usersboothjason@example.com Sat Dec 01 23:24:58 2007 Return-Path: <usersboothjason@example.com> Delivered-To: boothjason@example.com Received: (qmail 91897 invoked from network); 1 Dec 2007 23:24:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Dec 2007 23:24:58 -0000 Received: (qmail 95367 invoked by uid 500); 1 Dec 2007 23:24:44 -0000 Delivered-To: boothjason@example.com Received: (qmail 95350 invoked by uid 500); 1 Dec 2007 23:24:44 -0000 Mailing-List: contact boothjason@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:boothjason@example.com> List-Unsubscribe: <mailto:boothjason@example.com> List-Post: <mailto:boothjason@example.com> List-Id: <users.tapestry.apache.org> Reply-To: "Tapestry users" <boothjason@example.com> Delivered-To: mailing list boothjason@example.com Received: (qmail 95341 invoked by uid 99); 1 Dec 2007 23:24:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 15:24:44 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of boothjason@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO wa-out-1112.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 23:24:24 +0000 Received: by wa-out-1112.google.com with SMTP id j37so3997507waf for <boothjason@example.com>; Sat, 01 Dec 2007 15:24:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=QzZDGtn1TICEbvAxXLtHpFMrse172/88U4uaAxD8Do8=; b=M9tietPfAfBjIAV7PEpKMMwh/5psHEH7J9YX5Fa95Z0d0O6NI08SUyfuJwoWn0yZs8OlpTz4UdRiS4exqYv1YVvVIcjpdaJSSCE1iSCIGEhm0yGw2J2LpWkUjrmUOa/icAMYJJvS3r3wmUVFhgSpDWN2V1/AzCI1ADHwTxAb1fw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=hOra4QzFr8kqTKdpzDMuTKiAGJITq0P+3yBHAH9W/aK63Z90r2IpVIUSmwihzgI01gD0O6WpqqCidy/b+ZJRrGKXL2BUIH8l0IoQpD8PemR1q0tTjNajbhwUNhggKJZ4V32GZHiypJOSV4mB551wMh4H3hiCHYAWgfieSGcGiEM= Received: by 83.161.120.155 with SMTP id z17mr1707465wad.1196551466563; Sat, 01 Dec 2007 15:24:26 -0800 (PST) Received: by 83.161.120.155 with HTTP; Sat, 1 Dec 2007 15:24:26 -0800 (PST) Message-ID: <boothjason@example.com> Date: Sat, 1 Dec 2007 15:24:26 -0800 From: "Kalle Korhonen" <boothjason@example.com> To: "Tapestry users" <boothjason@example.com> Subject: Re: T4: From the client side, how do you programmatically update a component? In-Reply-To: <boothjason@example.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_5148_4522007.1196551466551" References: <boothjason@example.com> <boothjason@example.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_5148_4522007.1196551466551 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline No - I want to trigger the update programmatically via Javascript, not from a user's click. Kalle On 12/1/07, Ulrich St=E4rk <boothjason@example.com> wrote: > > I can't follow you. You want a component to update itself asynchronously > upon a user's click on a DirectLink? Why don't you just use DirectLink's > updateComponents parameter with async=3D"true"? > > Uli > > Kalle Korhonen schrieb: > > I have a use case where I need to "click on" a directllink to > > updatecomponents with async=3Dtrue or do an equivalent action in > Javascript. I > > know I can do tapestry.bind('<span boothjason@example.com.../>') and it ma= kes > > some sense, but looks rather ugly. Any cleaner way to accomplish this? > > > > Kalle > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: boothjason@example.com > For additional commands, e-mail: boothjason@example.com > > ------=_Part_5148_4522007.1196551466551-- From usersboothjason@example.com Sat Dec 01 23:58:58 2007 Return-Path: <usersboothjason@example.com> Delivered-To: boothjason@example.com Received: (qmail 96723 invoked from network); 1 Dec 2007 23:58:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Dec 2007 23:58:57 -0000 Received: (qmail 9504 invoked by uid 500); 1 Dec 2007 23:58:43 -0000 Delivered-To: boothjason@example.com Received: (qmail 9486 invoked by uid 500); 1 Dec 2007 23:58:43 -0000 Mailing-List: contact boothjason@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:boothjason@example.com> List-Unsubscribe: <mailto:boothjason@example.com> List-Post: <mailto:boothjason@example.com> List-Id: <users.tapestry.apache.org> Reply-To: "Tapestry users" <boothjason@example.com> Delivered-To: mailing list boothjason@example.com Received: (qmail 9477 invoked by uid 99); 1 Dec 2007 23:58:43 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 15:58:43 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of boothjason@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO ciao.gmane.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 23:58:44 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IycDz-0004AJ-IF for boothjason@example.com; Sat, 01 Dec 2007 23:58:19 +0000 Received: from 71-10-244-49.dhcp.oxfr.ma.charter.com ([83.161.120.155]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <boothjason@example.com>; Sat, 01 Dec 2007 23:58:19 +0000 Received: from kmenard by 71-10-244-49.dhcp.oxfr.ma.charter.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <boothjason@example.com>; Sat, 01 Dec 2007 23:58:19 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: boothjason@example.com From: Kevin Menard <boothjason@example.com> Subject: Re: Single OGNL expression evaluated several times =?ISO-8859-1?B?raA=?=is it normal? Date: Sat, 01 Dec 2007 18:58:08 -0500 Lines: 42 Message-ID: <boothjason@example.com> References: <boothjason@example.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Complaints-To: boothjason@example.com X-Gmane-NNTP-Posting-Host: 71-10-244-49.dhcp.oxfr.ma.charter.com User-Agent: Microsoft-Entourage/83.161.120.155618 Thread-Topic: Single OGNL expression evaluated several times =?ISO-8859-1?B?raA=?=is it normal? Thread-Index: Acg0dgVQQ665MKBpEdyR5QAbY5TfYw== Sender: news <boothjason@example.com> X-Virus-Checked: Checked by ClamAV on apache.org This is a known issue and is pending resolution. On 12/1/07 9:29 AM, in article boothjason@example.com, "Kaspar Fischer" <boothjason@example.com> wrote: > Hi, > > My Page.html contains a single Tapestry component: > > <title><span jwcid="@Insert" value="ognl:title">Title</span></title> > > Why is my page's method getTitle() executed several times? > > 15:23:11,106 User:admin DEBUG [knowledgecenter.pages.NodePage] > NodePage.pageBeginRender(). > 15:23:11,188 User:admin DEBUG [knowledgecenter.pages.NodePage] > NodePage.getTitle(). > 15:23:11,204 User:admin DEBUG [knowledgecenter.pages.NodePage] > NodePage.getTitle(). > 15:23:11,244 User:admin DEBUG [knowledgecenter.pages.NodePage] > NodePage.getTitle(). > 15:23:11,377 User:admin DEBUG [knowledgecenter.pages.NodePage] > NodePage.pageEndRender(). > > Is this normal or have I misconfigured Tapestry in some way? > > Kaspar > > --------------------------------------------------------------------- > To unsubscribe, e-mail: boothjason@example.com > For additional commands, e-mail: boothjason@example.com > > -- Kevin Menard Servprise International, Inc. Remote reboot & power control for network equipment www.servprise.com (646)582-0504 --------------------------------------------------------------------- To unsubscribe, e-mail: boothjason@example.com For additional commands, e-mail: boothjason@example.com From usersboothjason@example.com Sun Dec 02 02:32:25 2007 Return-Path: <usersboothjason@example.com> Delivered-To: boothjason@example.com Received: (qmail 64750 invoked from network); 2 Dec 2007 02:32:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Dec 2007 02:32:25 -0000 Received: (qmail 75400 invoked by uid 500); 2 Dec 2007 02:32:06 -0000 Delivered-To: boothjason@example.com Received: (qmail 75383 invoked by uid 500); 2 Dec 2007 02:32:06 -0000 Mailing-List: contact boothjason@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:boothjason@example.com> List-Unsubscribe: <mailto:boothjason@example.com> List-Post: <mailto:boothjason@example.com> List-Id: <users.tapestry.apache.org> Reply-To: "Tapestry users" <boothjason@example.com> Delivered-To: mailing list boothjason@example.com Received: (qmail 75374 invoked by uid 99); 2 Dec 2007 02:32:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 18:32:06 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of boothjason@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mxsf07.insightbb.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Dec 2007 02:32:09 +0000 X-IronPort-AV: E=Sophos;i="4.23,239,1194238800"; d="scan'208";a="152170300" Received: from unknown (HELO asav00.insightbb.com) ([83.161.120.155]) by mxsf07.insightbb.com with ESMTP; 01 Dec 2007 21:31:47 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAALKnUUdKjgBS/2dsb2JhbAAIkRI X-IronPort-AV: E=Sophos;i="4.23,239,1194238800"; d="scan'208";a="137279798" Received: from 74-142-0-82.dhcp.insightbb.com (HELO [83.161.120.155]) ([83.161.120.155]) by asav00.insightbb.com with ESMTP; 01 Dec 2007 21:31:46 -0500 Subject: Re: possible bug: onActivate/onDeactivate and ComponentActions From: Andy Huhn <boothjason@example.com> To: Tapestry users <boothjason@example.com> In-Reply-To: <boothjason@example.com> References: <boothjason@example.com> <boothjason@example.com> <boothjason@example.com> <boothjason@example.com> Content-Type: text/plain Date: Sat, 01 Dec 2007 21:31:46 -0500 Message-Id: <1196562706.7200.38.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I think console warnings are a great thing, and I hope you're not thinking about doing away with them! Maybe it's just because I'm a newbie, but I comb through those logs looking for problems if I get any unexpected behavior. Thanks, Andy On Sat, 2007-12-01 at 11:54 -0800, Howard Lewis Ship wrote: > Tapestry generates warnings about any non-private fields it finds in a > component class, so you might want to keep an eye on the console as > well. > > Sometimes I think console warnings are useless as no one ever seems to > see them, only by being "in your face" with a hard exception can you > catch the developers' attention. > > On Dec 1, 2007 11:17 AM, Fernando Padilla <boothjason@example.com> wrote: > > Yeah, they were public. Making all my variables private is one of those > > things I do without thinking, and I forgot to check that in this case. > > > > Funny. I don't remember reading about tapestry setting all private > > variables to null (or their default values) in the docs. Maybe I > > skimmed that part of the docs when I read them a while back. > > > > My apologies, setting them to private and having Tapestry set them to > > null should take care of it then. > > > > > > > > Howard Lewis Ship wrote: > > > What possible state would you have to clean up? > > > > > > Assuming you are using proper instance variables (all private), then > > > Tapestry already does end-of-request cleanup, resetting all your > > > fields to correct default values (for those that are not set to fixed > > > values via an injection). > > > > > > On Nov 30, 2007 6:34 PM, Fernando Padilla <boothjason@example.com> wrote: > > >> The bug we're seeing is that the page context is being set by an > > >> onActivate call, but it's never being cleaned up. So the next page > > >> render still has the old page context setup, and we don't have a chance > > >> to re-null it. > > >> > > >> > > >> > > >> normally while handling a page: > > >> > > >> onActivate > > >> setupRender > > >> ... > > >> cleanupRender > > >> > > >> We can absorb the context and cleanup anything that needs to be cleaned > > >> up within the "cleanupRender". But for ComponentActions, there is no > > >> such "cleanup" method available: > > >> > > >> onActivate > > >> onAction > > >> > > >> > > >> > > >> Proposed solution is really easy, just add an "onDeactivate" event. > > >> Allowing us to undo any page activation. > > >> > > >> > > >> ideas? > > >> > > >> > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: boothjason@example.com > > >> For additional commands, e-mail: boothjason@example.com > > >> > > >> > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: boothjason@example.com > > For additional commands, e-mail: boothjason@example.com > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: boothjason@example.com For additional commands, e-mail: boothjason@example.com From usersboothjason@example.com Sun Dec 02 03:50:57 2007 Return-Path: <usersboothjason@example.com> Delivered-To: boothjason@example.com Received: (qmail 79317 invoked from network); 2 Dec 2007 03:50:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Dec 2007 03:50:56 -0000 Received: (qmail 16614 invoked by uid 500); 2 Dec 2007 03:50:38 -0000 Delivered-To: boothjason@example.com Received: (qmail 16604 invoked by uid 500); 2 Dec 2007 03:50:37 -0000 Mailing-List: contact boothjason@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:boothjason@example.com> List-Unsubscribe: <mailto:boothjason@example.com> List-Post: <mailto:boothjason@example.com> List-Id: <users.tapestry.apache.org> Reply-To: "Tapestry users" <boothjason@example.com> Delivered-To: mailing list boothjason@example.com Received: (qmail 16595 invoked by uid 99); 2 Dec 2007 03:50:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 19:50:37 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of boothjason@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mxsf05.insightbb.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Dec 2007 03:50:18 +0000 X-IronPort-AV: E=Sophos;i="4.23,239,1194238800"; d="scan'208";a="135467424" Received: from unknown (HELO asav00.insightbb.com) ([83.161.120.155]) by mxsf05.insightbb.com with ESMTP; 01 Dec 2007 22:50:18 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAHK6UUdKjgBS/2dsb2JhbAAI X-IronPort-AV: E=Sophos;i="4.23,239,1194238800"; d="scan'208";a="137290088" Received: from 74-142-0-82.dhcp.insightbb.com (HELO [83.161.120.155]) ([83.161.120.155]) by asav00.insightbb.com with ESMTP; 01 Dec 2007 22:50:20 -0500 Subject: T5: fixed-width Grid? From: Andy Huhn <boothjason@example.com> To: Tapestry users <boothjason@example.com> Content-Type: text/plain Date: Sat, 01 Dec 2007 22:50:17 -0500 Message-Id: <1196567417.7200.50.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org All, Is there a way to make a Grid fixed-width? That is, if it's more than x number of pixels, a scroll bar is rendered attached to the HTML table? (Not attached to the entire viewport). Thanks, Andy --------------------------------------------------------------------- To unsubscribe, e-mail: boothjason@example.com For additional commands, e-mail: boothjason@example.com From usersboothjason@example.com Sun Dec 02 03:53:13 2007 Return-Path: <usersboothjason@example.com> Delivered-To: boothjason@example.com Received: (qmail 79775 invoked from network); 2 Dec 2007 03:53:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Dec 2007 03:53:13 -0000 Received: (qmail 17739 invoked by uid 500); 2 Dec 2007 03:52:58 -0000 Delivered-To: boothjason@example.com Received: (qmail 17725 invoked by uid 500); 2 Dec 2007 03:52:58 -0000 Mailing-List: contact boothjason@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:boothjason@example.com> List-Unsubscribe: <mailto:boothjason@example.com> List-Post: <mailto:boothjason@example.com> List-Id: <users.tapestry.apache.org> Reply-To: "Tapestry users" <boothjason@example.com> Delivered-To: mailing list boothjason@example.com Received: (qmail 17716 invoked by uid 99); 2 Dec 2007 03:52:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 19:52:58 -0800 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of boothjason@example.com does not designate 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO out1.smtp.messagingengine.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Dec 2007 03:53:00 +0000 Received: from compute1.internal (compute1.internal [83.161.120.155]) by out1.messagingengine.com (Postfix) with ESMTP id A931859AA1 for <boothjason@example.com>; Sat, 1 Dec 2007 22:52:39 -0500 (EST) Received: from heartbeat1.messagingengine.com ([83.161.120.155]) by compute1.internal (MEProxy); Sat, 01 Dec 2007 22:52:39 -0500 X-Sasl-enc: g1yb3O2tVQlp204zLlIInZSreJHTIJWYPUx/CyNlthrM 1196567558 Received: from 180.sub-70-212-158.myvzw.com (180.sub-70-212-158.myvzw.com [83.161.120.155]) by mail.messagingengine.com (Postfix) with ESMTP id 7C4F41E77 for <boothjason@example.com>; Sat, 1 Dec 2007 22:52:38 -0500 (EST) Message-ID: <boothjason@example.com> Date: Sat, 01 Dec 2007 19:52:34 -0800 From: Fernando Padilla <boothjason@example.com> User-Agent: Thunderbird 83.161.120.155 (Macintosh/20071031) MIME-Version: 1.0 To: Tapestry users <boothjason@example.com> Subject: Re: possible bug: onActivate/onDeactivate and ComponentActions References: <boothjason@example.com> <boothjason@example.com> <boothjason@example.com> <boothjason@example.com> In-Reply-To: <boothjason@example.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org The problem is that we develop with debug. And in tapestry it prints out the full generated source of the page as debug, basically making the first few requests on the webapp totally useless as far as debug goes... is there any way to make that source easier for us to parse out? move it to TRACE or move it to a different log category easier for us to turn on and off? Howard Lewis Ship wrote: > Tapestry generates warnings about any non-private fields it finds in a > component class, so you might want to keep an eye on the console as > well. > > Sometimes I think console warnings are useless as no one ever seems to > see them, only by being "in your face" with a hard exception can you > catch the developers' attention. > > On Dec 1, 2007 11:17 AM, Fernando Padilla <boothjason@example.com> wrote: >> Yeah, they were public. Making all my variables private is one of those >> things I do without thinking, and I forgot to check that in this case. >> >> Funny. I don't remember reading about tapestry setting all private >> variables to null (or their default values) in the docs. Maybe I >> skimmed that part of the docs when I read them a while back. >> >> My apologies, setting them to private and having Tapestry set them to >> null should take care of it then. >> >> >> >> Howard Lewis Ship wrote: >>> What possible state would you have to clean up? >>> >>> Assuming you are using proper instance variables (all private), then >>> Tapestry already does end-of-request cleanup, resetting all your >>> fields to correct default values (for those that are not set to fixed >>> values via an injection). >>> >>> On Nov 30, 2007 6:34 PM, Fernando Padilla <boothjason@example.com> wrote: >>>> The bug we're seeing is that the page context is being set by an >>>> onActivate call, but it's never being cleaned up. So the next page >>>> render still has the old page context setup, and we don't have a chance >>>> to re-null it. >>>> >>>> >>>> >>>> normally while handling a page: >>>> >>>> onActivate >>>> setupRender >>>> ... >>>> cleanupRender >>>> >>>> We can absorb the context and cleanup anything that needs to be cleaned >>>> up within the "cleanupRender". But for ComponentActions, there is no >>>> such "cleanup" method available: >>>> >>>> onActivate >>>> onAction >>>> >>>> >>>> >>>> Proposed solution is really easy, just add an "onDeactivate" event. >>>> Allowing us to undo any page activation. >>>> >>>> >>>> ideas? >>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: boothjason@example.com >>>> For additional commands, e-mail: boothjason@example.com >>>> >>>> >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: boothjason@example.com >> For additional commands, e-mail: boothjason@example.com >> >> > > > --------------------------------------------------------------------- To unsubscribe, e-mail: boothjason@example.com For additional commands, e-mail: boothjason@example.com From usersboothjason@example.com Sun Dec 02 04:26:18 2007 Return-Path: <usersboothjason@example.com> Delivered-To: boothjason@example.com Received: (qmail 85521 invoked from network); 2 Dec 2007 04:26:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Dec 2007 04:26:18 -0000 Received: (qmail 30103 invoked by uid 500); 2 Dec 2007 04:26:04 -0000 Delivered-To: boothjason@example.com Received: (qmail 30092 invoked by uid 500); 2 Dec 2007 04:26:04 -0000 Mailing-List: contact boothjason@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:boothjason@example.com> List-Unsubscribe: <mailto:boothjason@example.com> List-Post: <mailto:boothjason@example.com> List-Id: <users.tapestry.apache.org> Reply-To: "Tapestry users" <boothjason@example.com> Delivered-To: mailing list boothjason@example.com Received: (qmail 30082 invoked by uid 99); 2 Dec 2007 04:26:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 20:26:04 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of boothjason@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO kuber.nabble.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Dec 2007 04:26:07 +0000 Received: from isper.nabble.com ([83.161.120.155]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from <boothjason@example.com>) id 1IygOo-00041n-Ko for boothjason@example.com; Sat, 01 Dec 2007 20:25:46 -0800 Message-ID: <boothjason@example.com> Date: Sat, 1 Dec 2007 20:25:46 -0800 (PST) From: Angelo Chen <boothjason@example.com> To: boothjason@example.com Subject: Re: T5: fixed-width Grid? In-Reply-To: <1196567417.7200.50.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: boothjason@example.com References: <1196567417.7200.50.camel@localhost> X-Virus-Checked: Checked by ClamAV on apache.org Hi Andy, I can't quite understand your question, I use css to made grid fixed-width, usually I use only one cell from the grid: .id-header { width:780px; } then in the grid I can include other fields in the cell, this will not work if you want to have sortable columns: <table t:type="grid" source="rows" row="row" > <t:parameter name="idCell"> ${row.id} ${row.field1} ${row.field2} </t:parameter> Andy Huhn wrote: > > All, > > Is there a way to make a Grid fixed-width? That is, if it's more than x > number of pixels, a scroll bar is rendered attached to the HTML table? > (Not attached to the entire viewport). > > Thanks, > Andy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: boothjason@example.com > For additional commands, e-mail: boothjason@example.com > > > -- View this message in context: http://www.nabble.com/T5%3A-fixed-width-Grid--tf4930497.html#a14112576 Sent from the Tapestry - User mailing list boothjason@example.com. --------------------------------------------------------------------- To unsubscribe, e-mail: boothjason@example.com For additional commands, e-mail: boothjason@example.com From usersboothjason@example.com Sun Dec 02 04:35:13 2007 Return-Path: <usersboothjason@example.com> Delivered-To: boothjason@example.com Received: (qmail 87076 invoked from network); 2 Dec 2007 04:35:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Dec 2007 04:35:13 -0000 Received: (qmail 36714 invoked by uid 500); 2 Dec 2007 04:34:54 -0000 Delivered-To: boothjason@example.com Received: (qmail 36704 invoked by uid 500); 2 Dec 2007 04:34:54 -0000 Mailing-List: contact boothjason@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:boothjason@example.com> List-Unsubscribe: <mailto:boothjason@example.com> List-Post: <mailto:boothjason@example.com> List-Id: <users.tapestry.apache.org> Reply-To: "Tapestry users" <boothjason@example.com> Delivered-To: mailing list boothjason@example.com Received: (qmail 36695 invoked by uid 99); 2 Dec 2007 04:34:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 20:34:54 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of boothjason@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO kuber.nabble.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Dec 2007 04:34:33 +0000 Received: from isper.nabble.com ([83.161.120.155]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from <boothjason@example.com>) id 1IygXM-0004DS-BI for boothjason@example.com; Sat, 01 Dec 2007 20:34:36 -0800 Message-ID: <boothjason@example.com> Date: Sat, 1 Dec 2007 20:34:36 -0800 (PST) From: Angelo Chen <boothjason@example.com> To: boothjason@example.com Subject: T5: Select's model MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: boothjason@example.com X-Virus-Checked: Checked by ClamAV on apache.org Hi, I use a TreeMap for the 'Select' component, it works but it is always sorted in the key order, not the name of country when showing to the user, i read somewhere it can be a list, any suggestions, sample codes? thanks. A.C. public TreeMap<String, String> getCountryList() {return ...} <input t:type="select" t:id="country" model="countryList" t:value="country" /><br/> -- View this message in context: http://www.nabble.com/T5%3A-Select%27s-model-tf4930588.html#a14112599 Sent from the Tapestry - User mailing list boothjason@example.com. --------------------------------------------------------------------- To unsubscribe, e-mail: boothjason@example.com For additional commands, e-mail: boothjason@example.com From usersboothjason@example.com Sun Dec 02 05:17:58 2007 Return-Path: <usersboothjason@example.com> Delivered-To: boothjason@example.com Received: (qmail 5105 invoked from network); 2 Dec 2007 05:17:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Dec 2007 05:17:58 -0000 Received: (qmail 63241 invoked by uid 500); 2 Dec 2007 05:17:39 -0000 Delivered-To: boothjason@example.com Received: (qmail 63221 invoked by uid 500); 2 Dec 2007 05:17:39 -0000 Mailing-List: contact boothjason@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:boothjason@example.com> List-Unsubscribe: <mailto:boothjason@example.com> List-Post: <mailto:boothjason@example.com> List-Id: <users.tapestry.apache.org> Reply-To: "Tapestry users" <boothjason@example.com> Delivered-To: mailing list boothjason@example.com Received: (qmail 63212 invoked by uid 99); 2 Dec 2007 05:17:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 01 Dec 2007 21:17:39 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of boothjason@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO wa-out-1112.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Dec 2007 05:17:20 +0000 Received: by wa-out-1112.google.com with SMTP id j37so4180573waf for <boothjason@example.com>; Sat, 01 Dec 2007 21:17:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=XD556/M9UunSZreYHWNVQCeFIjiKP7zcpwIywrvaY84=; b=gpJUIZZw99x7tPaINcwtmzXQp7ZjMTDuD3mymxi2ORhxssQqYhCcVQpY+60WDJ6phF33l4qvXrvGCtA72NKhYBSduqGin8d1DHFKCBCJqoXklTWmWO3z/zGcAmDqyHvw2waLD9pMFTK7ODsv6INTVbaQRPs+RCk6BW0rfkWW57U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dCtou+vT3M5rbESXCV1ta8lviBxLw4g09ZZWTymg3mC/0mY8ypc2yc3DXqkBz6/qLTjnqNsy4VsYAfULRWUzcMuiD00xsp9xxHkITWTRfKCCFxBIyFiSSzEPIq+mUYIpUvD9VgRGtpSeOFuxmfQhc0K0Fl6BPncZ7TJ7VhmSyuA= Received: by 83.161.120.155 with SMTP id k19mr1202596wfg.1196572643518; Sat, 01 Dec 2007 21:17:23 -0800 (PST) Received: by 83.161.120.155 with HTTP; Sat, 1 Dec 2007 21:17:23 -0800 (PST) Message-ID: <boothjason@example.com> Date: Sun, 2 Dec 2007 10:47:23 +0530 From: lasitha <boothjason@example.com> To: "Tapestry users" <boothjason@example.com> Subject: Re: T5: Tapestry-Hibernate, do we have to save()? In-Reply-To: <op.t11f6tmrovlrp5@porsche> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <boothjason@example.com> <boothjason@example.com> <boothjason@example.com> <op.t018imppovlrp5@porsche> <boothjason@example.com> <op.t11f6tmrovlrp5@porsche> X-Virus-Checked: Checked by ClamAV on apache.org On Nov 19, 2007 5:42 PM, Thiago H de Paula Figueiredo <boothjason@example.com> wrote: > On Mon, 19 Nov 2007 07:17:32 -0200, lasitha <boothjason@example.com> > wrote: > > [.... a long descpription on the 'unintended save' problem ...] > > > On Oct 31, 2007, Thiago H de Paula Figueiredo <boothjason@example.com> wrote: > > > > Thiago, any chance you'll be releasing the source [of HiberTapestry] soon? > > I'm planning to release the sources until this weekend. Thiago, thanks for releasing that, i've finally had some time to look into it this weekend. Looks neat - well done :). Some thoughts relevant to the 'unintended save' problem: * I think HiberTapestry mostly solves it. * The only hole i can see is that even though we only commit explicitly at the successful completion of a @Transactional method, i think it's possible that hibernate will automatically flush the session at unexpected moments. The default FlushMode.AUTO documentation specifies: "The Session is sometimes flushed before query execution in order to ensure that queries never return stale state". If this happens before we are ready, we may still be open to unintentional saves. Would it be safer to set the flush mode to COMMIT instead? More general feedback: * In our own solution to the problem (see below), we found it useful to be able to annotate page/component methods. In fact i think our most common case is to mark the onSuccess event as the commit point. Since tapestry-ioc doesn't decorate pages and components, we are contributing a ComponentClassTransformWorker that injects the transactional code into pages. This may be some neat functionality to add to HiberTapestry. * I'm not sure if https://issues.apache.org/jira/browse/TAPESTRY-1874 is still valid. I am able to get Match("*") to work without tapestry complaning about IOC services. Might be something to look into as it would elimante the naming convention limitation. Our homegrown solution so far: * We override and alias the HibernateSessionManager so that it always _rolls back_ on thread cleanup. * We set the flush mode to AUTO (also by overriding the HSM). * We introduce a @CommitOnCompletion annotation that tells the framework to call HSM.commit() when the marked method completes. This will commit the transaction that was begun when the session was first created, and begin a new one for the rest of the request cycle. If the method is never called or hits an exception everything is rolled back. If you see any problem with that solution, please let us know. In any case, i suspect this whole problem will be superceded by the (hopefully) upcoming support for 'conversations'. Be well, lasitha. P.S. I am leaving my current job (and considering a career change :), so i may not do a good job of following up on this thread. My apologies in advance. --------------------------------------------------------------------- To unsubscribe, e-mail: boothjason@example.com For additional commands, e-mail: boothjason@example.com From usersboothjason@example.com Sun Dec 02 13:35:31 2007 Return-Path: <usersboothjason@example.com> Delivered-To: boothjason@example.com Received: (qmail 97130 invoked from network); 2 Dec 2007 13:35:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Dec 2007 13:35:31 -0000 Received: (qmail 8912 invoked by uid 500); 2 Dec 2007 13:35:16 -0000 Delivered-To: boothjason@example.com Received: (qmail 8899 invoked by uid 500); 2 Dec 2007 13:35:16 -0000 Mailing-List: contact boothjason@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:boothjason@example.com> List-Unsubscribe: <mailto:boothjason@example.com> List-Post: <mailto:boothjason@example.com> List-Id: <users.tapestry.apache.org> Reply-To: "Tapestry users" <boothjason@example.com> Delivered-To: mailing list boothjason@example.com Received: (qmail 8890 invoked by uid 99); 2 Dec 2007 13:35:15 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Dec 2007 05:35:15 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of boothjason@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO kuber.nabble.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Dec 2007 13:35:18 +0000 Received: from isper.nabble.com ([83.161.120.155]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from <boothjason@example.com>) id 1IyoyH-0006cx-4J for boothjason@example.com; Sun, 02 Dec 2007 05:34:57 -0800 Message-ID: <boothjason@example.com> Date: Sun, 2 Dec 2007 05:34:57 -0800 (PST) From: Angelo Chen <boothjason@example.com> To: boothjason@example.com Subject: T5: Map and persistency MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: boothjason@example.com X-Virus-Checked: Checked by ClamAV on apache.org Hi, One thing confuses me, here is a sample code: private Map<String, String> countryList; @Inject private DBServices dbServices; void pageLoaded() { countryList = dbServices.getCountryList(); without any Persist annotation, the countryList is persisted between requests. if I move the above line to the constructor of the page class, it has the same result. why? A.C. -- View this message in context: http://www.nabble.com/T5%3A-Map-and-persistency-tf4931665.html#a14115516 Sent from the Tapestry - User mailing list boothjason@example.com. --------------------------------------------------------------------- To unsubscribe, e-mail: boothjason@example.com For additional commands, e-mail: boothjason@example.com From usersboothjason@example.com Sun Dec 02 14:42:58 2007 Return-Path: <usersboothjason@example.com> Delivered-To: boothjason@example.com Received: (qmail 5700 invoked from network); 2 Dec 2007 14:42:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Dec 2007 14:42:58 -0000 Received: (qmail 41317 invoked by uid 500); 2 Dec 2007 14:42:42 -0000 Delivered-To: boothjason@example.com Received: (qmail 41293 invoked by uid 500); 2 Dec 2007 14:42:42 -0000 Mailing-List: contact boothjason@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:boothjason@example.com> List-Unsubscribe: <mailto:boothjason@example.com> List-Post: <mailto:boothjason@example.com> List-Id: <users.tapestry.apache.org> Reply-To: "Tapestry users" <boothjason@example.com> Delivered-To: mailing list boothjason@example.com Received: (qmail 41284 invoked by uid 99); 2 Dec 2007 14:42:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Dec 2007 06:42:42 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of boothjason@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO ciao.gmane.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Dec 2007 14:42:43 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IypyV-0007bp-Ax for boothjason@example.com; Sun, 02 Dec 2007 14:39:15 +0000 Received: from 71-10-244-49.dhcp.oxfr.ma.charter.com ([83.161.120.155]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <boothjason@example.com>; Sun, 02 Dec 2007 14:39:15 +0000 Received: from kmenard by 71-10-244-49.dhcp.oxfr.ma.charter.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <boothjason@example.com>; Sun, 02 Dec 2007 14:39:15 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: boothjason@example.com From: Kevin Menard <boothjason@example.com> Subject: Re: T5: Select's model Date: Sun, 02 Dec 2007 09:34:34 -0500 Lines: 72 Message-ID: <boothjason@example.com> References: <boothjason@example.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Complaints-To: boothjason@example.com X-Gmane-NNTP-Posting-Host: 71-10-244-49.dhcp.oxfr.ma.charter.com User-Agent: Microsoft-Entourage/83.161.120.155618 Thread-Topic: T5: Select's model Thread-Index: Acg08HUDs3aAFqDjEdyaPgAbY5TfYw== Sender: news <boothjason@example.com> X-Virus-Checked: Checked by ClamAV on apache.org You can just create an instance of SelectModelImpl. To simplify things a bit, I've just implemented the interface and delegated to a SelectModelImpl instance. public class ProductTypeSelectModel implements SelectModel { private final SelectModel model; public ProductTypeSelectModel(final ObjectContext context) { final List<OptionModel> options = new ArrayList<OptionModel>(); final SelectQuery query = new SelectQuery(ProductType.class); query.addOrdering(ProductType.NAME_PROPERTY, true); final List<ProductType> productTypes = (List<ProductType>) context.performQuery(query); options.add(new OptionModelImpl("None (root level)", false, null)); for (final ProductType pt : productTypes) { options.add(new OptionModelImpl(pt.getName(), false, pt)); } model = new SelectModelImpl(null, options); } public List<OptionGroupModel> getOptionGroups() { return model.getOptionGroups(); } public List<OptionModel> getOptions() { return model.getOptions(); } public void visit(final SelectModelVisitor visitor) { model.visit(visitor); } } This example uses Cayenne to query for my "product_types" and sorts them by name. Even if you're not familiar with Cayenne, it should be fairly straightforward. On 12/1/07 11:34 PM, in article boothjason@example.com, "Angelo Chen" <boothjason@example.com> wrote: > > Hi, > > I use a TreeMap for the 'Select' component, it works but it is always sorted > in the key order, not the name of country when showing to the user, i read > somewhere it can be a list, any suggestions, sample codes? thanks. > > A.C. > > public TreeMap<String, String> getCountryList() {return ...} > > <input t:type="select" t:id="country" model="countryList" t:value="country" > /><br/> > -- Kevin Menard Servprise International, Inc. Remote reboot & power control for network equipment www.servprise.com (646)582-0504 --------------------------------------------------------------------- To unsubscribe, e-mail: boothjason@example.com For additional commands, e-mail: boothjason@example.com From usersboothjason@example.com Sun Dec 02 14:46:35 2007 Return-Path: <usersboothjason@example.com> Delivered-To: boothjason@example.com Received: (qmail 6199 invoked from network); 2 Dec 2007 14:46:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Dec 2007 14:46:35 -0000 Received: (qmail 44440 invoked by uid 500); 2 Dec 2007 14:46:20 -0000 Delivered-To: boothjason@example.com Received: (qmail 44422 invoked by uid 500); 2 Dec 2007 14:46:20 -0000 Mailing-List: contact boothjason@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:boothjason@example.com> List-Unsubscribe: <mailto:boothjason@example.com> List-Post: <mailto:boothjason@example.com> List-Id: <users.tapestry.apache.org> Reply-To: "Tapestry users" <boothjason@example.com> Delivered-To: mailing list boothjason@example.com Received: (qmail 44413 invoked by uid 99); 2 Dec 2007 14:46:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Dec 2007 06:46:20 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of boothjason@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO ciao.gmane.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Dec 2007 14:46:20 +0000 Received: from root by ciao.gmane.org with local (Exim 4.43) id 1Iyq46-0001Ly-Fx for boothjason@example.com; Sun, 02 Dec 2007 14:45:02 +0000 Received: from 71-10-244-49.dhcp.oxfr.ma.charter.com ([83.161.120.155]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <boothjason@example.com>; Sun, 02 Dec 2007 14:45:02 +0000 Received: from kmenard by 71-10-244-49.dhcp.oxfr.ma.charter.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <boothjason@example.com>; Sun, 02 Dec 2007 14:45:02 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: boothjason@example.com From: Kevin Menard <boothjason@example.com> Subject: Re: T5: Map and persistency Date: Sun, 02 Dec 2007 09:36:31 -0500 Lines: 31 Message-ID: <boothjason@example.com> References: <boothjason@example.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Complaints-To: boothjason@example.com X-Gmane-NNTP-Posting-Host: 71-10-244-49.dhcp.oxfr.ma.charter.com User-Agent: Microsoft-Entourage/83.161.120.155618 Thread-Topic: T5: Map and persistency Thread-Index: Acg08LrA+Qcg1qDjEdyaPgAbY5TfYw== Sender: news <boothjason@example.com> X-Virus-Checked: Checked by ClamAV on apache.org Are you sure it's
{'source': 'Apache Software Foundation Public Mail Archives'}