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 86980 invoked from network); 26 Apr 2000 15:15:33 -0000 Received: from mta4.rcsntx.swbell.net (151.164.30.28) by locus.apache.org with SMTP; 26 Apr 2000 15:15:33 -0000 Received: from [209.184.0.61] by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FTM00KCTQCZAW@mta4.rcsntx.swbell.net> for cocoon-dev@xml.apache.org; Wed, 26 Apr 2000 10:15:00 -0500 (CDT) Date: Wed, 26 Apr 2000 10:15:07 -0500 From: Mike Engelhart Subject: Re: Specifying an XSL in a Cocoon Request In-reply-to: <14599.1859.992598.295249@dsl-216-227-26-85.chi.interchangedsl.com> To: cocoon-dev@xml.apache.org Message-id: MIME-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Lee Burgess wrote: > For example, what if I don't want to use XSP; that is, I don't want > that kind of logic in my XML? > > A custom Producer seems the way to go, but that is a pain because one > essentially has to add an extra layer of file parsing and/or object > instantiation just to set the xml-stylesheet PI in the XML before it > gets sent off to the Processor. The XML basically ends up getting > parsed twice: once in the custom Producer and then again in the course > of normal cocoon processing. Lee, An XSP is a custom producer. It's just that it gets compiled from an XSP page on it's first run (ala JSP). Mike