The following comment has been added to this issue:
Author: Michael Glavassevich
Created: Wed, 14 Apr 2004 9:00 AM
Body:
Thanks Naela. I modified the patch slightly to fix some NPEs. It's in CVS now. I'll
mark this resolved once I'm able to change the state.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/XERCESJ-944?page=comments#action_35021
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/XERCESJ-944
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XERCESJ-944
Summary: Allow 'schema-location', 'schema-type' parameters to be set with null
value
Type: Bug
Status: Unassigned
Priority: Minor
Project: Xerces2-J
Components:
DOM
Versions:
2.6.2
Assignee:
Reporter: Naela Nissar
Created: Tue, 13 Apr 2004 3:12 PM
Updated: Wed, 14 Apr 2004 9:00 AM
Description:
L3 Core Spec states that setting a parameter to null should unset the parameter. For
'schema-location' and 'schema-type' domConfiguration parameters, allow them to be set
null in DOMParserImpl and DOMConfigurationImpl setParameter methods. Also,
canSetParameter in DOMParserImpl should accordingly return true when querying with a
null value for these parameters, as well as 'resource-resolver' and 'error-handler'.
On a very minor note, getParameterNames() in DOMParserImpl adds DOM_ENTITIES twice.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
