-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Giacomo Pati wrote: > Hi all > > If there is nobody working on the subject I'll spend a few hours on doing > that. > > My general tactic would be to first rewrite the xconf/rules into a spring > config so that adding new > Widgets/Converters/Datatypes will than be easily manageable (using bean-maps) > and than see how the > classes have to be rewritten to follow that. > > Any better ideas? Now that I'm trying to do it I have some qustions about how we can manage LifecycleHelper stuff in a Spring context. In CForm definition files there are constructs that accepted a class attribute to denote a Java class being instantiated and managed as it where a Avalon Component (Validators, SelectionLists, and more). Whats the oppinion of other on this subject. I'd like to get rid of LifecycleHelpre at all (it is already deprecated) but this will probably lead to incompatabilities with the old CForm. WDOT? - -- Giacomo Pati Otego AG, Switzerland - http://www.otego.com Orixo, the XML business alliance - http://www.orixo.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.6 (GNU/Linux) iD8DBQFG7mfvLNdJvZjjVZARAtXmAKDXjXllUV6QzNYUtpn1a+UQWk6TnwCcCtLu uAzfDYdggRUkYsH3fPKV8sw= =8Y/u -----END PGP SIGNATURE-----
