Return-Path: Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 13672 invoked by uid 98); 12 Dec 2002 10:47:57 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Received: (qmail 13653 invoked from network); 12 Dec 2002 10:47:54 -0000 Received: from daedalus.apache.org (HELO apache.org) (63.251.56.142) by nagoya.betaversion.org with SMTP; 12 Dec 2002 10:47:54 -0000 Received: (qmail 49871 invoked by uid 500); 12 Dec 2002 10:46:32 -0000 Received: (qmail 49863 invoked from network); 12 Dec 2002 10:46:32 -0000 Received: from mail.paranor.ch (HELO nts?par1.paranor.ch) (195.65.4.180) by daedalus.apache.org with SMTP; 12 Dec 2002 10:46:32 -0000 Received: by nts_par1.paranor.ch with Internet Mail Service (5.5.2448.0) id ; Thu, 12 Dec 2002 11:46:44 +0100 Message-ID: <36E996B162DAD111B6AF0000F879AD1A76C061@nts_par1.paranor.ch> From: "Wannheden, Knut" To: "Jakarta-Commons-User (E-mail)" Subject: [jelly] xml pipeline Date: Thu, 12 Dec 2002 11:46:43 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I just read the new article about the Jelly XML pipeline at http://jakarta.apache.org/commons/sandbox/jelly/pipeline.html. It is stated that a Jelly Tag can choose how to invoke its body. So it could (amongst other things) evaluate its body based on some condition or parse its body into some structure. This seems to suggest that these are two completely different modes of operation. But AFAICT, the second usage (parse the body) requires it to be evaluated first. Wouldn't it be useful if a Tag could decide to parse its body in "raw" format (no evaluation of it) or get the body as XML (DOM or SAX)? So for example in the would retrieve its body as a Script. For this Script it could either request the associated XML code or evaluate it (and optionally get the output). Cheers, -- knut