Pavani writes:
>Please find the attached patch for AbstractSAXParser.
>parse(inputSource) throws a NullPointerException if 'inputSource' is null.
> + if (inputSource == null) {
> + throw new SAXException("InputSource is null");
> + }
This seems like an unusual change to make to the Java implementation
of a service. We could add hundreds of such checks where users are
passing null in place of a required parameter. What is the rationale
that the application should not receive a NullPointerException when
they are in fact passing a null pointer ? This is not a SAX error
per se, but a programming error in using a Java API and Java has
defined such exceptions for this purpose.
Regards,
Glenn
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
