Return-Path: Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 33606 invoked from network); 10 Jul 2000 22:28:13 -0000 Received: from frankfurt.denic.de (HELO notes.denic.de) (194.246.96.101) by locus.apache.org with SMTP; 10 Jul 2000 22:28:13 -0000 Received: from denics7 ([192.168.0.63]) by notes.denic.de (Lotus Domino Version 5.0.2c (Intl)) with ESMTP id 2000071100271446:3149 ; Tue, 11 Jul 2000 00:27:14 +0200 Date: Tue, 11 Jul 2000 00:27:18 +0200 (MET DST) From: Uli Mayring To: cocoon-users@xml.apache.org Subject: Re: built sql query In-Reply-To: Message-ID: "X-Ncc-RegID: de.denic" MIME-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on notes/Denic(Version 5.0.2c (Intl)|08 Februar 2000) at 11.07.2000 00:27:14, Serialize by Router on notes/Denic(Version 5.0.2c (Intl)|08 Februar 2000) at 11.07.2000 00:27:27, Serialize complete at 11.07.2000 00:27:27 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 10 Jul 2000, Donald Ball wrote: > why in the world do y'all insist on mixing sqlprocessor with xsp? if > you're using xsp, use the sql logicsheet! if there's something wrong with > it, do tell! For one thing the 64K limit for Java methods doesn't affect a processor, but it does affect an XSP taglib :-) The next thing is that with the SQL processor I have better control over processing order, because I can decide whether I put it before or after an XSP pass. BTW, why didn't you implement XInclude as an XSP taglib, but as a processor? I suspect the answer to that question tells you something about SQL processor vs. SQL taglib. I think we need both, processor and taglib. Ulrich -- Ulrich Mayring DENIC eG, Softwareentwicklung