From commons-dev-return-75495-apmail-jakarta-commons-dev-archive=jakarta.apache.org@jakarta.apache.org Wed Aug 10 22:14:57 2005 Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 192 invoked from network); 10 Aug 2005 22:14:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Aug 2005 22:14:55 -0000 Received: (qmail 12122 invoked by uid 500); 10 Aug 2005 22:14:53 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 12030 invoked by uid 500); 10 Aug 2005 22:14:52 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 12017 invoked by uid 99); 10 Aug 2005 22:14:52 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Aug 2005 15:14:52 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [134.96.188.26] (HELO mail.dfki.de) (134.96.188.26) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Aug 2005 15:15:14 -0700 Received: from mail.dfki.de (localhost.dfki.uni-sb.de [127.0.0.1]) by localhost (Postfix) with ESMTP id 1B849E481E for ; Thu, 11 Aug 2005 00:14:45 +0200 (CEST) Received: from [IPv6:::1] (dave.dfki.uni-sb.de [134.96.184.220]) by mail.dfki.de (Postfix) with ESMTP id BC312E47D4 for ; Thu, 11 Aug 2005 00:14:44 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v622) In-Reply-To: References: <4819F1B2A1DF9E4688D69213B9566444066671@srvexch01.tecit.intra> <26094526-D049-4BB8-A9EF-93D02A7DA791@apache.org> <51266B03-7CC4-4C14-B79D-45D77B319974@apache.org> <0885a5de31eab8527a843b64f7646439@activemath.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: Paul Libbrecht Subject: Re: [jelly] 1.0-final problem wrt tag caching Date: Thu, 11 Aug 2005 00:14:42 +0200 To: "Jakarta Commons Developers List" X-Mailer: Apple Mail (2.622) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Peter, I'm annoyed... I don't obtain the same results as you do. With the default cacheTags value as false, I obtain only your test=20 failing. With the default cacheTags value as true, I obtain many failed tests. Did you not say that with your commit, all jelly-core tests were=20 passing ? If not then we really need to push the NeedCaching and RefusesCaching=20 interfaces. Right ? paul Le 4 ao=FBt 05, =E0 03:27, peter royal a =E9crit : > On Jul 23, 2005, at 4:12 PM, Paul Libbrecht wrote: >> Two things that are particularly picky and for which we need some=20 >> form tag-caching: >> >> - define'd tags ? >> - the swing:action tag. >> >> For the latter, things are particularly bad since you want to invoke=20= >> the action on the bean of a tag (a component, say, that you want to=20= >> change) without changing that component... >> >> But... I'll let you experiment. > > The unit tests for both of these taglibs passed with=20 > JellyContext.isCacheTags restored, so I've committed the change. > > I'd like to pursue the interface that means 'cache me' so we can move=20= > forward with caching :) > -pete > > --=20 > peter royal > --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org