> > Exactly. I opened a Bugzilla ticket for this issue (#36447) and fixed
> it.
> >
>
> Just to clarify, do you mean that if I have the following config...
>
> <props>
> <url>http://www.boo.com/</url>
> <url>http://www.hoo.com/</url>
> <url>http://www.foo.com/</url>
> </props>
>
> And I did...
>
> config.getProperty("url");
>
> I would get only the first value, which is "http://www.boo.com/";?
No. The case that we were talking about is when the property is used during
interpolation (substitution). For example, if you had an extra property
<url>http://www.boo.com/</url>
<url>http://www.hoo.com/</url>
<url>http://www.foo.com/</url>
<myresource>${url}myresource.html</myresource>
The issue here is, should the entire list ("http://www.boo.com/,
http://www.hoo.com/, ...") be used to substitute into "myresource"?
I take it that Oliver's fix will be to have Config.getProperty("myresource")
return
http://www.boo.com/myresource.html
But you'll have to check bugzilla as to what the fix will look like.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
