Return-Path: Delivered-To: apmail-jakarta-taglibs-dev-archive@apache.org Received: (qmail 21989 invoked from network); 29 Nov 2002 22:39:34 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 29 Nov 2002 22:39:34 -0000 Received: (qmail 181 invoked by uid 97); 29 Nov 2002 22:40:28 -0000 Delivered-To: qmlist-jakarta-archive-taglibs-dev@jakarta.apache.org Received: (qmail 46 invoked by uid 97); 29 Nov 2002 22:40:27 -0000 Mailing-List: contact taglibs-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tag Libraries Developers List" Reply-To: "Tag Libraries Developers List" Delivered-To: mailing list taglibs-dev@jakarta.apache.org Received: (qmail 29894 invoked by uid 98); 29 Nov 2002 22:40:26 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3DE7EC95.2030603@mail.more.net> Date: Fri, 29 Nov 2002 16:39:17 -0600 From: Glenn Nielsen Organization: MOREnet User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0.0) Gecko/20020909 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tag Libraries Developers List Subject: Re: JspTagLifecycle: Testing JSP tag libraries with Cactus References: <3DE4E821.5020703@gmx.de> <3DE72C25.4080705@gmx.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Christopher Lenz wrote: > Hi again, > > considering the overwhelming response to this mail (not ;-) ), I'm gonna > add some more: > The taglib lists are a bit slow, and this is a four day holdiay in the states. So please be patient. :-) I am aware of Cactus but haven't had time to play with it yet. It is on my list of technologies I want to research and possibly incorporate into development/testing where I work. :-) It looks like the test suite uses a servlet container but not the container's JSP engine. JSP custom tags and their behaviour is very tightly coupled to the JSP engine the custom tag lib is running within. Things like JSP engine custom tag pooling, etc. can have a big impact on whether tags work correctly. I wonder how useful a test suite like this would be when it doesn't also test the container JSP engine. Setting up test cases using actual JSP pages then making sure you get back the correct response is much more complete testing of both the tags and the JSP engine IMHO. Regards, Glenn -- To unsubscribe, e-mail: For additional commands, e-mail: