cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <>
Subject Re: Springifying CForms: How to solve LifecycleHelper stuff
Date Mon, 17 Sep 2007 14:32:06 GMT
Hash: SHA1

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?

>>> What I also would like to see, but it might be outside you current
>>> scope, is to get rid of the selectors. I would prefer a solution where
>>> maps with widgets, data types and so on are created with the bean-map
>>> and these maps are injected into the form manager.
>> This is absolutely in my scope. I don't want to see those Avalon
>> ServiceSelector again ;-)
> Great!
> /Daniel

- --
Giacomo Pati
Otego AG, Switzerland -
Orixo, the XML business alliance -

Version: GnuPG v2.0.6 (GNU/Linux)


View raw message