Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 44062 invoked from network); 22 May 2000 23:03:11 -0000 Received: from pop.systemy.it (194.20.140.28) by locus.apache.org with SMTP; 22 May 2000 23:03:11 -0000 Received: from apache.org (pv22-pri.systemy.it [194.21.255.22]) by pop.systemy.it (8.8.8/8.8.3) with ESMTP id BAA05869 for ; Tue, 23 May 2000 01:03:09 +0200 Message-ID: <3929B165.44219168@apache.org> Date: Tue, 23 May 2000 00:15:01 +0200 From: Stefano Mazzocchi Organization: Apache Software Foundation X-Mailer: Mozilla 4.72 [en] (Windows NT 5.0; I) X-Accept-Language: en,it MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: [Cocoon2] XSP 2.0 changes list References: <39295A98.93467EAB@apache.org> <20000522202734.A22048@brit.luminas.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Paul Russell wrote: > > On Mon, May 22, 2000 at 01:58:25PM -0400, Donald Ball wrote: > > > 6) Taglib creation kit > > > > > > This to simplify the creation of taglibs. > > > > ha! would love to see it, but i don't see it happening. > > Heh. Cynic ;) > > Stefano: What exactly did you intend this to comprise? > I *guess* it would be kindof the XSP 'SDK'... Currently people are scared by XSP taglibs. I admit I'm scared too and prefer to write "normal" XSLT logicsheets, that work more like tag expansion that anything. Ricardo wrote most of the taglibs and has his hands in everyone that's been written (not many, in fact). I, myself, never wrote an XSP taglib. Why? well, a few reasons: 1) there is no documentation on how to do this. Taglibs were introduced by Ricardo in what should have become XSP 1.1 or XSP layer 2 (as we used to call it). Layer 3 should have been the introduction to XBeans, which would represent the merging of EJB and XML. Layer2 got integreated into mainstream and never wanted to write something because, in all honesty, I didn't believe that much in taglibs. But I've changed my mind and I do see their main role for separation of logic and content. Layer3 is more or less JSP-bullshit and we never did any serious resoning on that. (Note that even some of the Servlet Experts expressed their concerns about J2EE marketing crap) 2) you need to know how to create code that merges with the compiled page without generating errors. 3) you need a way to _debug_ your compiled pages and avoid the "black box" syndrome where the code that goes either comes out fine or generates a (more or less random) compilation problem. (this is, in general, a problem with compiled server pages, but taglibs make this even worse). I think Ricardo has more ideas on how to make this simple. I'll let him talk about it.... -- Stefano Mazzocchi One must still have chaos in oneself to be able to give birth to a dancing star. Friedrich Nietzsche -------------------------------------------------------------------- Missed us in Orlando? Make it up with ApacheCON Europe in London! ------------------------- http://ApacheCon.Com ---------------------