[
https://issues.apache.org/jira/browse/XERCESJ-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Glavassevich resolved XERCESJ-1544.
-------------------------------------------
Resolution: Invalid
There is no such restriction. Please refer to the specification [1].
An attribute may have been defaulted from an XML Schema, in which case there
may not be a prefix available, even if the attribute has a namespace.
Namespace-aware serializers (e.g. LSSerializer) will fix up the prefixes and
namespace declarations when the DOM is written to XML.
[1] http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-DocCrAttrNS
> set/createAttributeNS allows creation of unqualified namespaced attributes
> --------------------------------------------------------------------------
>
> Key: XERCESJ-1544
> URL: https://issues.apache.org/jira/browse/XERCESJ-1544
> Project: Xerces2-J
> Issue Type: Bug
> Components: DOM (Level 3 Core)
> Affects Versions: 2.10.0
> Reporter: Anli Shundi
>
> Maybe I'm missing something trivial here but I'm surprised even with error
> checking on DOM allows me to create an attribute with a namespace but with no
> prefix. I.e. it allows the qualifiedName to be unqualified. The default
> prefix doesn't apply to attributes ...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: j-dev-h...@xerces.apache.org
