Providing the constructor of ValidatorResources with a null InputStream leads to a MalformedURLException,
which leads the user (trying to find his error) in a complete wrong direction. Perhaps returning a NullPointerException or
an IllegalArgumentException seems to be a better understandable reaction.
Description
Providing the constructor of ValidatorResources with a null InputStream leads to a MalformedURLException,
which leads the user (trying to find his error) in a complete wrong direction. Perhaps returning a NullPointerException or
an IllegalArgumentException seems to be a better understandable reaction.
Niall Pemberton added a comment - 26/Feb/07 05:19 PM Thanks for reporting this - I've fixed this in validator (now throws an IllegalArgumentException indicating that the InputStream is null).
I also created an issue for this against Commons Digester (DIGESTER-111) - which also failed to check that the InputStream isn't null.
Niall
I also created an issue for this against Commons Digester (
DIGESTER-111) - which also failed to check that the InputStream isn't null.Niall