cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Gallardo" <agalla...@agsoftware.dnsalias.com>
Subject Re: [RT] Improving Sitemap and Flowscript
Date Wed, 20 Aug 2003 10:57:28 GMT
<note>
I resend again this post, since I dont got it in my mailbox. It seems like
the 2 virus in the wild (Sobig.f and MSBlast) are causing major troubles
in the Internet...

Please stop using the major virus called Windows ;-D

</note>

> So, after making a request for this a few days ago, with some people's
help (a suggestion to look into mounted sitemaps) there seems to be an
already existing solution. Rather than adding extra functionality to
support doing this in cocoon.xconf, wouldn't it make more sense to just
ship an extra sitemap with the default distribution? It could exist in
WEB-INF as like base.xmap or something and be referenced in cocoon.xconf
as the main sitemap.

:) +1 I think it could be called "components.xconf" since it is all about.

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?

Note: merging <map:components> and cocoon.xconf will be worse. Newbies
tend to keep away from cocooon.xconf because they simple does not
understand it (I said that based in my own experience).

Best Regards,

Antonio Gallardo




Mime
View raw message