Nicola Ken Barozzi <[EMAIL PROTECTED]> writes:
>> If you want XML based configuration, you should add an adaptor to the
>> commons-configuration and simply use it. That way, people who want to
>> keep their properties files won't get fucked up.
>Or send us a patch so that Avalon can use property files for
>configuration. A Configuration is not necessarily based on XML, just our
>default implementation is.
So basically your position is "we're Avalon. We convert what we
consider useful to work with us and don't care if any other project
using these components falls wayside. Either you adapt or die".
Sounds like the Borg. Maybe some of the Turbine developers will now start
to understand my sceptical position on "avalonization".
I'm working on the turbine project. I'm trying to support my needs and
the needs of the turbine users. The patch for avalon is easy: Use
commons-configuration and write an adaptor that can read avalon XML
configuration files and present them as a Configuration object. End of
Story.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH [EMAIL PROTECTED]
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 [EMAIL PROTECTED]
D-91054 Buckenhof Fax.: 09131 / 50654-20
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
