cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reinhard Poetz <>
Subject Re: Springifying CForms: How to solve LifecycleHelper stuff
Date Mon, 17 Sep 2007 14:35:44 GMT
Giacomo Pati wrote:
> Daniel Fagerstrom wrote:
>> Giacomo Pati skrev:
>>> Daniel Fagerstrom wrote:
>>>> Giacomo Pati skrev:
>>> Again, how should deprecation be implemented:
>>> a) use deprecation logger but keep current implementation
>>> b) throw an exception and remove current implementation
>> a) is probably the correct solution, but at least I would prefer b). To
>> me, the class attribute in forms for creating components seem like some
>> hack or workaround that hopefully very few depends on.
> I think we should vote on this, shouldn't we? I absolutely dislike having the LifecycleHelper
> thus Avalon classes) staying in the CForms code.
> What do otehrs think about it?

I don't like them either. I would vote +1.

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

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


View raw message