On Thu, 1 Dec 2005, Matt Benson <[EMAIL PROTECTED]> wrote: > BTW, doesn't this type negate the need for the > "javaresource" and "classpath" attributes and nested > <classpath> elements of <url>? ;)
To tell the truth I forgot they were there. When I modified loadproperties I quickly looked over the list of built-in resources to find the name of the type for resources read from the CLASSPATH and no, it never occured to me that <url> could do that. I was surprised not to find one and added javaresource. I discovered <url> could do it after the fact, but still think javaresource is the better way to go (probably others don't tie ClassLoader.getResource() with URLs either). And javaresource already supports classpathref and loaderref 8-) Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
