cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <>
Subject Re: Springifying CForms
Date Fri, 14 Sep 2007 14:23:32 GMT
Hash: SHA1

Grzegorz Kossakowski wrote:
> Giacomo Pati pisze:
>> Hi all
> Hi Giacomo
>> If there is nobody working on the subject I'll spend a few hours on doing that.
> I'm very pleased to see that you want to work on this as it has been on my wish-list
for quite long
> time. However, I'm not sure if you remember that we are going to have next release in
a week[1]. I
> just realized that Reinhard omitted CForms on that list but I guess it was just oversight.

I don't think I can manage that until release date.

> Since moving towards Spring is not trivial step I wouldn't like to see it done for Forms
1.0.0 but

I'm quite familiar with Spring _and_ Avalon

> for 1.1.0. That raises natural question: do we want to branch Forms block? I would be
in favour of
> such solution if there is no other one.

I could copy it to whiteboard but have to sync it with changes in trunk by hand (without help

>> 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?
> I think your plan is good and I will be happy to help if there are some problems as I
have been
> Springifying some code in Cocoon, already. I'm curious if you want to completely move
away from
> Avalon and convert whole code not only configuration handling?

Sure, completely.

> [1]

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

Version: GnuPG v2.0.6 (GNU/Linux)


View raw message