cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <>
Subject Re: Manually specifying a mounted sub sitemap's context
Date Sun, 10 Apr 2005 20:17:11 GMT
Gianugo Rabellino wrote:

>On Apr 10, 2005 4:24 PM, Stefano Mazzocchi <> wrote:
>>Sylvain Wallez wrote:
>>>So, although we may accept a new "context" attribute (I'm currently -0.9
>>>for this), I'm -1 for accepting dynamically generated sitemaps.
>>I'm -1 as well. (that was easy to guess ;-)
>Uhm, first of all I'd say that the "context" attribute could be really
>useful in contexts other than dynamic sitemaps, so I'd welcome that
>addition. WRT dynamic sitemaps, I don't quite have a real opinion, I
>can clearly see how it might lead to abuse, but I also tend to think
>that Cocoon, as a framework, should allow applications built on top of
>it using subsets of functionalities abstracted in high level
>configuration files. However, if it's agreed once and for all that
>dynamic sitemaps are to be considered harmful, so be it and let's
>enforce it: it slipped through already, and now it doesn't work
>anymore because of a bug. A check failing with an error message would
>be enough to prevent stupid people like me to try it again in the
>future (even though there will always be the http route...).

Well, as long as there is the http route, blocking "cocoon:" will just 
lead people to use an uglier workaround which you just engraved in the 
archives for posterity ;-)

So if we're to enforce something, it should be that a sitemap is a file, 
or a classpath resource (yes, I have this usecase).


Sylvain Wallez                        Anyware Technologies  
Apache Software Foundation Member     Research & Technology Director

View raw message