Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 2653 invoked by uid 500); 24 Apr 2001 10:29:00 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 1914 invoked from network); 24 Apr 2001 10:28:55 -0000 Date: Tue, 24 Apr 2001 12:32:08 +0200 From: Sandor Spruit X-Mailer: The Bat! (v1.49) Personal Reply-To: Sandor Spruit Organization: Information and computing sciences, Utrecht University X-Priority: 3 (Normal) Message-ID: <858630059.20010424123208@cs.uu.nl> To: cocoon-users@xml.apache.org Subject: [C1] Detailed question about creating a custom logicsheet Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N cocoon-users, In short: I've written a custom logicsheet in order to process some custom XSP elements (headers, footers), used in various XSP pages across my experimental site. Can I introduce elements via this logicsheet, say ESQL elements, to be processed by some subsequent XSP processing step ? If so, what pitfalls are there? Example: my logicsheet expands a "header" tag in my own namespace to a series of ESQL tags. Upon processing, these tags gets replaced by database query statements that insert information about the current user at the top of the page. Sounds reasonable, right ? Any ideas ? Sandor -- ir A.G.L. Spruit, Utrecht University, the Netherlands Institute of information and computing sciences "There is a bit of magic in everything, and then some loss to even things out" (from: Lou Reed, "Magic and Loss") --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: