Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 80520 invoked by uid 500); 8 Jun 2001 13:53:59 -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 80161 invoked from network); 8 Jun 2001 13:53:52 -0000 X-Authentication-Warning: holsten.uni-koblenz.de: flatty owned process doing -bs Date: Fri, 8 Jun 2001 15:53:20 +0200 (CEST) From: "Jens-A. Reinhardt" X-X-Sender: To: , =?ISO-8859-1?Q?Beno=EEt_Chauvet?= Subject: Re: [C1] chaining XSP and Xinclude In-Reply-To: <014f01c0f01f$baa28780$26ed430a@bchauvet> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On Fri, 8 Jun 2001, Beno=EEt Chauvet wrote: > Hi dear cocoon users and hackers, > > Reading for past messages on this Mailing-list, I've found confirmation t= hat multiple XSP processing couldn't be chained... > > But what about xinclude ? xinclude can be applied a couple of times. If you use xinclude before XSP than the included content becomes part of the compiled XSP java class and thus static with regard to the original sources (until the class file is recompiled e.g. if the original xml file changes) If you call XInclude after the XSP than the xinclude will be performed each time you request the file. Jens --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. To unsubscribe, e-mail: For additional commands, e-mail: