Jason van Zyl wrote:
>
> Jon Stevens wrote:
>
> > on 3/7/01 10:49 PM, "Jason van Zyl" <[EMAIL PROTECTED]> wrote:
> >
> > > resource.loader = file
> > > resource.loader = classpath
> >
> > +1
> >
> > > classpath.resource.loader.description = Classpath Resource Loader
> >
> > I'm -0, meaning I don't like this part and I don't care enough to really
> > argue my point.
> >
> > I would still prefer it being:
> >
> > resource.loader.classpath.description
>
> Ok, now I remeber why I did it as well. Looking at
>
> 1)
> resource.loader = file
> resource.loader = classpath
>
> resource.loader.file.<prop> = <value>
>
> versus
>
> 2)
> resource.loader = file
> resource.loader = classpath
>
> file.resource.loader.<prop> = <value>
>
> If I want to grab just the resource loaders then I will use
>
> Configuration. subset("resource.loader") I'm going to get all the config
> stuff for the resource loaders too, I don't want that.
>
> Where in 2) performing Configuration.subset("resource.loader")
> will simply give me back the two configuration entries I expect.
> Then I can use those values ('file', 'classpath') to retrieve the
> values for each individual loader.
>
> So I think we have to keep it in the form
>
> <id>.resource.loader.<prop> = value
>
> In order to make it easy to parse internally, I think it reads more
> like a sentence that way too.
>
> Is this ok?
>
While I still think that Jons suggestion is the most logical, would be
easy to read, I will happily support the other way if we get the .N
stuff for repeated and Runtime.setProperty() deals in the right way :)
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
Developing for the web? See http://jakarta.apache.org/velocity/
