You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@xerces.apache.org by "Kristian Ivarsson (JIRA)" <xe...@xml.apache.org> on 2009/04/09 11:38:13 UTC

[jira] Created: (XERCESC-1861) DOMLSResourceResolver or DOMLSParser fails to use system identifier in DOMLSInput

DOMLSResourceResolver or DOMLSParser fails to use system identifier in DOMLSInput
---------------------------------------------------------------------------------

                 Key: XERCESC-1861
                 URL: https://issues.apache.org/jira/browse/XERCESC-1861
             Project: Xerces-C++
          Issue Type: Bug
          Components: DOM
    Affects Versions: 3.0.1
         Environment: Solaris and Windows XP
            Reporter: Kristian Ivarsson
            Priority: Minor


This might be a documentation defect (as well)

When implementing the interface DOMLSResourceResolver::resolveResource() and using DOMLSInput::setSystemId() but without DOMLSInput::setByteStream() before returning the DOMLSInput-object, the application core-dumps, despite that the documentation (and sort of the standard as well) says "the parser will attempt to open a URI connection to the resource identified by the system identifier" (as a last resort)

The documentation for DOMLSResourceResolver::resolveResource() does not explicity say who's the owner of any possible byte stream set to the (soon to be) adopted DOMLSInput and therefore one might feel tempted to not setting any byte stream to the input-object to risk any memory-leaks, but since that doesn't work one end up in a catch 22 scenario



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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