imo, as long as the javadoc is clear enough, any behavior is ok.
What's written in current version is:
name - resource to be added, the classpath is examined for a file with that
So nothing in this javadoc lets you believe that the file exists or will be
loaded. Also you could make sure your file is in the classpath (which is
the case for me).
2013/1/17 Jay Vyas <[EMAIL PROTECTED]>
> Good catch with that string.length() - you're right, that was a silly
> mistake. --- sorry - im not sure what i was thinking. it was a late night
> In any case, the same code with file.exists() fails... i've validated
> that path many ways.
> On a broader note: Shouldn't the Configuration class just throw a
> RuntimeException if the file isn't available? Its very strange to add
> all these default resources, which may or may not exist, to a class - then
> having to introspect on the class at runtime to see if they actually got
> On Thu, Jan 17, 2013 at 5:06 AM, Julien Muller <[EMAIL PROTECTED]>wrote:
> Jay Vyas