cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jay Freeman \(saurik\)" <>
Subject Re: [RT] Improving Sitemap and Flowscript
Date Wed, 20 Aug 2003 21:28:18 GMT

The complaint I would have about a complete seperation of sitemaps (rather
than my original "sitemap override" proposal, or my revised "just use
mounted subsitemaps") is that then, if you have a particular component that
you want in your app, or a particular configuration of an existing one,
you're back modifying the base sitemap. I would want components to be
capable of going in either, and subsitemaps do that without "any" changes to
the overall code :).

Jay Freeman (saurik)

----- Original Message -----
From: "Antonio Gallardo" <>
To: <>
Sent: Wednesday, August 20, 2003 5:57 AM
Subject: Re: [RT] Improving Sitemap and Flowscript

> I think it could not be a big change if we separate the current
> sitemap.xmap in:
> WEB-INF/components.xconf    -> <map:components> part of current
> sitemap.xmap sitemap.xmap                -> just <map:pipelines>
> To dont make the change to "traumatic" to the overall code, initially we
> can specialize a class of the current sitemap processor that just will
> merge this to files in in once and give the control back to the "current
> sitemap processor".
> What do you think?
> Best Regards,
> Antonio Gallardo

View raw message