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 ji...@apache.org on 2004/04/14 00:12:43 UTC
[jira] Created: (XERCESJ-944) Allow 'schema-location', 'schema-type' parameters to be set with null value
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
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: Tue, 13 Apr 2004 3:12 PM
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: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
[jira] Updated: (XERCESJ-944) Allow 'schema-location', 'schema-type' parameters to be set with null value
Posted by ji...@apache.org.
The following issue has been updated:
Updater: Naela Nissar (mailto:nnissar@ca.ibm.com)
Date: Tue, 13 Apr 2004 3:13 PM
Comment:
Proposed patch to allow null for parameter value
Changes:
Attachment changed to NullSetting.txt
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/XERCESJ-944?page=history
---------------------------------------------------------------------
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: Tue, 13 Apr 2004 3:13 PM
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: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
[jira] Resolved: (XERCESJ-944) Allow 'schema-location', 'schema-type' parameters to be set with null value
Posted by ji...@apache.org.
Message:
The following issue has been resolved as FIXED.
Resolver: Michael Glavassevich
Date: Fri, 23 Apr 2004 10:26 AM
Thanks Naela. The 2nd patch is in CVS now.
---------------------------------------------------------------------
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: Resolved
Priority: Minor
Resolution: FIXED
Project: Xerces2-J
Components:
DOM
Fix Fors:
2.6.2
Versions:
2.6.2
Assignee: Michael Glavassevich
Reporter: Naela Nissar
Created: Tue, 13 Apr 2004 3:12 PM
Updated: Fri, 23 Apr 2004 10:26 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: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
[jira] Updated: (XERCESJ-944) Allow 'schema-location', 'schema-type' parameters to be set with null value
Posted by ji...@apache.org.
The following issue has been updated:
Updater: Naela Nissar (mailto:nnissar@ca.ibm.com)
Date: Wed, 14 Apr 2004 12:02 PM
Comment:
Patch to add DOM_SPLIT_CDATA to list in getParameterNames() in DOMParserImpl
Changes:
Attachment changed to addSplitCdata.txt
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/XERCESJ-944?page=history
---------------------------------------------------------------------
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: Resolved
Priority: Minor
Resolution: FIXED
Project: Xerces2-J
Components:
DOM
Fix Fors:
2.6.2
Versions:
2.6.2
Assignee:
Reporter: Naela Nissar
Created: Tue, 13 Apr 2004 3:12 PM
Updated: Wed, 14 Apr 2004 12:02 PM
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: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
[jira] Resolved: (XERCESJ-944) Allow 'schema-location', 'schema-type' parameters to be set with null value
Posted by ji...@apache.org.
Message:
The following issue has been resolved as FIXED.
Resolver: Michael Glavassevich
Date: Wed, 14 Apr 2004 10:48 AM
Resolved. See previous comment.
---------------------------------------------------------------------
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: Resolved
Priority: Minor
Resolution: FIXED
Project: Xerces2-J
Components:
DOM
Fix Fors:
2.6.2
Versions:
2.6.2
Assignee:
Reporter: Naela Nissar
Created: Tue, 13 Apr 2004 3:12 PM
Updated: Wed, 14 Apr 2004 10:48 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: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
[jira] Commented: (XERCESJ-944) Allow 'schema-location', 'schema-type' parameters to be set with null value
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Naela Nissar
Created: Wed, 14 Apr 2004 12:01 PM
Body:
There is one more very minor change needed to getParameterNames() in DOMParserImpl. Constants.DOM_SPLIT_CDATA must be added to the list of parameter names supported. DOM LS test LSParserConfig2 is failing as a result. If it would be better to open this as a new bug, please let me know.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/XERCESJ-944?page=comments#action_35029
---------------------------------------------------------------------
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: Resolved
Priority: Minor
Resolution: FIXED
Project: Xerces2-J
Components:
DOM
Fix Fors:
2.6.2
Versions:
2.6.2
Assignee:
Reporter: Naela Nissar
Created: Tue, 13 Apr 2004 3:12 PM
Updated: Wed, 14 Apr 2004 12:01 PM
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: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
[jira] Reopened: (XERCESJ-944) Allow 'schema-location', 'schema-type' parameters to be set with null value
Posted by ji...@apache.org.
Message:
The following issue has been reopened.
Reopener: Michael Glavassevich
Date: Fri, 23 Apr 2004 8:50 AM
Reopening for another bug in DOMParserImpl.
---------------------------------------------------------------------
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: Reopened
Priority: Minor
Project: Xerces2-J
Components:
DOM
Fix Fors:
2.6.2
Versions:
2.6.2
Assignee: Michael Glavassevich
Reporter: Naela Nissar
Created: Tue, 13 Apr 2004 3:12 PM
Updated: Fri, 23 Apr 2004 8:50 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: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org
[jira] Commented: (XERCESJ-944) Allow 'schema-location', 'schema-type' parameters to be set with null value
Posted by ji...@apache.org.
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: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org