cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <>
Subject Re: [RT] Flow as a block
Date Wed, 19 Mar 2003 14:31:23 GMT
Stefano Mazzocchi wrote:

> Sylvain Wallez wrote:
>> Carsten Ziegeler wrote:

>>> Could the treeprocessor check the availability of a class before 
>>> feeding
>>> it into the selector? If the class is not available, a dummy 
>>> implementation
>>> could be perhaps added that could - when used - throw a meaningfull
>>> exception. 
>> Well, this would mean rewriting a ComponenentSelector specifically 
>> for this purpose, since the TreeProcessor does nothing more than 
>> delegating all this stuff to a CS : see 
>> DefaultTreeBuilder.createBuilderSelector().
>> Mmmh... A good solution may be to have a FakeFlowNodeBuilder that 
>> delegates to a RealFlowNodeBuilder if it's present in the classpath, 
>> and otherwise fails with a nice error message saying that the flow 
>> isn't installed.
>> That way, we don't have to open wide the sitemap language definition, 
>> which could lead to abuses : map:flow becomes an optional element 
>> that is however pre-configured in the sitemap definition. Just drop 
>> in the flow jar and it becomes available, without touching a single 
>> configuration file.
>> Thoughts ?
> I personally don't like it. Adding fake facades for just one thing 
> doesn't sound right at all.


Please let's do without kludges.


View raw message