Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 14309 invoked by uid 500); 24 Oct 2001 22:03:05 -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 14294 invoked from network); 24 Oct 2001 22:03:04 -0000 Message-ID: <022d01c15cd7$a9bb1a20$6401a8c0@ad.eoncompany.com> From: "Christer Lindh" To: Subject: how to implement a dynamic sitemap? Date: Thu, 25 Oct 2001 00:03:06 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_022A_01C15CE8.6C8C8100" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ------=_NextPart_000_022A_01C15CE8.6C8C8100 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable As far as I've understood C2, there is now a quite static sitemap which = tells what request gets what XSL. This is too static for my needs, I = would like to do a bunch of calculations and then decide on what XSL to = use. Is there any way I can accomplish this with C2? I have my own producer today with Cocoon 1 which creates Documents from = data in my database, and these are then assigned an XSL depending on a = bunch of parameters (from the database and user environment as well), ie = I add PI:s to the Document DOM dynamically. So - is it possible to use "classic" cocoon1.8 processing instructions = with cocoon2, instead of specifying processing stages in the sitemap? If not, can I do my own implement of the Sitemap interfaces and get C2 = to use those instead? My classes would act just like a sitemap (as the = interfaces are the same) but get it's daata from database instead of a = XML file in the filesystem. ------=_NextPart_000_022A_01C15CE8.6C8C8100 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
As far as I've understood C2, there is = now a quite=20 static sitemap which tells what request gets what XSL. This is too=20 static for my needs, I would like to do a bunch of calculations and = then=20 decide on what XSL to use. Is there any way I can accomplish this with=20 C2?
 
I have my own producer today with = Cocoon=20 1 which creates Documents from data in my database, and these are = then=20 assigned an XSL depending on a bunch of parameters (from the database = and user=20 environment as well), ie I add PI:s to the Document DOM=20 dynamically.
 
So - is it possible to use "classic" cocoon1.8 processing = instructions with=20 cocoon2, instead of specifying processing stages in the = sitemap?
 
If not, can I do my own implement of = the Sitemap=20 interfaces and get C2 to use those instead?  My classes would act = just like=20 a sitemap (as the interfaces are the same) but get it's daata from = database=20 instead of a XML file in the filesystem.
 
 
 
------=_NextPart_000_022A_01C15CE8.6C8C8100--