Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 37017 invoked by uid 500); 13 Feb 2002 13:33:13 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 37001 invoked from network); 13 Feb 2002 13:33:12 -0000 Message-ID: <9916289167D2D411BD0700508BB4A527E66FF5@dvntex01.devote.nl> From: Michael Homeijer To: cocoon-dev@xml.apache.org Subject: XML serializer adaption to simplify Client side XSLT Date: Wed, 13 Feb 2002 14:26:21 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Hi, I want to use client side XSL translation in Cocoon. I have a pipeline that aggregates content from several sources that should be rendered at the client. I could solve this by rendering it at the server by a stylesheet that just adds a processing instruction, but I think this should be something that a serializer is able to do. Can somebody give me some hints on how to add this to the XML serializer or implement it in an ClientSideXSLTSerializer? Does this make sense or do I have some kind of syndrom ;-) TIA, Michael Homeijer --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org