IMO, this is the closest to the correct solution.
For me, the correct way to do it is to have a separate configuration
mechanism. Just build an interface somewhere (Runtime?) to set configuration
values (properties) and get whatever configurator that suits your needs.
For the sake of ease-of-use, Runtime should use a default configuration
mechanism to initialize itself on first use - if no other initialization was
performed before. This default mechanism could just be the Properties based
one that is now used, so that the current behaviour is not changed.
If this default Properties configurator is loaded "by name", people that
prefer XML-configurators or whatever-configurators don't even need to have
the default configurator present.
This also allows for easier programatic onfiguration directly from Servlet
code using some application specific stuff.
So, as usual, I prefer having a default behaviour and the option to plug
alternative ones.
Have fun,
Paulo
PS: I still owe some patches. They are not forgotten and I will build them.
> -----Original Message-----
> From: jeff [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, March 06, 2001 06:44
> To: [EMAIL PROTECTED]
> Subject: Re: [Proposal] Velocity Release Plan 1.0
>
>
> How about whoever wants to use Properties: make an adapter that converts a
> Properties to a Configuration, add it to the contrib directory and then be
> done with this discussion.
>
> Or something.
>
>
>
