cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Poetz <>
Subject Re: The real Processor concerns
Date Wed, 12 Oct 2005 11:17:14 GMT
Carsten Ziegeler wrote:
> Reinhard Poetz wrote:
>>Carsten Ziegeler wrote:
>>>>Hm :-) Are you sure it will be better than SitemapConfigurable? :-)
>>>No :) Ok, for example we could have properties file next to the sitemap
>>>and these properties are available as global variables for this sitemap
>>>and all sub sitemaps. This might be a little bit cleaner. Don't no.
>>Maybe I miss the point completly as I haven't followed this thread in detail, 
>>but aren't block properties (declared in block.xml and set in wiring.xml) enough?
> Yes, gosh, you're right - the only question is, do we want to go this
> way and do this incompatible changes (means: removing the sitemap
> component configurations from the sitemap)?

then deprecate it in 2.1 and remove it in 2.2

As long as our users don't run blindly into such changes, it isn't a problem. 
The deprecation logger and a note in the "Update Cocoon 2.1 to 2.2 docs" should 
be enough.

Reinhard Pötz           Independent Consultant, Trainer & (IT)-Coach 

{Software Engineering, Open Source, Web Applications, Apache Cocoon}


View raw message