Paulo Gaspar wrote:
> >
> > resource.loader.1 = file
> > resource.loader.2 = classpath
> >
> > which will
> >
> > ...
>
> Doesn't declaration order work the same way?
Yes, but here it's explicit. And then internal properties parser can
check to ensure that the user clearly specified their intent, and log
it.
> I confess I do not sympathize with the number suffixes - more editing work
> changing the order of a group of properties (ok... some keystrokes more!).
Ok. The main advantage is that we don't prevent anyone from using a
Properties, Hashtable, Hashmap, Treemap, etc... to hold this stuff. It
keeps them unique, and in a easy pattern to parse.
Given the good idea of eliminating the 'integer in the middle' that
keeps the loader properties distinct, having them at the end when you
mean 'multiple-valued property' is a nice and easy way to do it.
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
