You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by "Michael Glavassevich (JIRA)" <xe...@xml.apache.org> on 2005/06/23 20:01:23 UTC

[jira] Resolved: (XERCESJ-1083) Error reporting when schema can't be found throws null pointer exception

     [ http://issues.apache.org/jira/browse/XERCESJ-1083?page=all ]
     
Michael Glavassevich resolved XERCESJ-1083:
-------------------------------------------

    Resolution: Fixed

Thanks for reporting. I've applied fix to CVS, though I wasn't able to find a scenario which induces the NPE.

> Error reporting when schema can't be found throws null pointer exception
> ------------------------------------------------------------------------
>
>          Key: XERCESJ-1083
>          URL: http://issues.apache.org/jira/browse/XERCESJ-1083
>      Project: Xerces2-J
>         Type: Bug
>   Components: XML Schema Structures
>     Reporter: Alex Milowski
>  Attachments: XMLSchemaValidator.java.diff
>
> Using the code for the current CVS Head, a null pointer is thrown inside XMLSchemaValidator
> on line 2413, when the code is reporting the error.  The call fXSDDescription.getLocationHints()
> can return a null pointer, as it does in my environment.
> I am running XMLSchemaValidator alone in a custom environment.  While it is possible
> that something is misconfigured, no exceptions are thrown when the document's
> schema can be found.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org