[
https://issues.apache.org/jira/browse/XMLBEANS-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580590#comment-13580590
]
Martin Spamer commented on XMLBEANS-446:
----------------------------------------
This issue should NOT be classified as minor.
It causes a fatal errors with ALL correctly specified W3C name space extensions.
It is a clear miss-interpretation of the specification and relatively easy fix,
removing these lines
3324 if (beginsWithXml(prefix) &&
3325 !("xml".equals(prefix) && _xml1998Uri.equals(uri)))
3326 {
3327 XmlError err =
3328 XmlError.forMessage(
3329 "Prefix can't begin with XML: " + prefix,
3330 XmlError.SEVERITY_ERROR);
3331
3332 throw new XmlRuntimeException(err.toString(), null, err);
3333
from org.apache.xmlbeans.impl.store.Locale
> too restrictive prefix constraint
> ---------------------------------
>
> Key: XMLBEANS-446
> URL: https://issues.apache.org/jira/browse/XMLBEANS-446
> Project: XMLBeans
> Issue Type: Bug
> Affects Versions: Version 2.3, Version 2.4 , Version 2.5
> Reporter: Vojtech Janota
> Priority: Minor
>
> XML Specification clearly states that when declaring namespace bindings
> prefixes starting with "xml" are reserved and must not be used. However it
> also states that processors must NOT treat them as fatal errors. Current
> implementation fails to parse XML files with such prefixes:
> org.apache.xmlbeans.XmlRuntimeException: error: Prefix can't begin with XML:
> xml2uddi_portType
> at
> org.apache.xmlbeans.impl.store.Locale$SaxHandler.startPrefixMapping(Locale.java:3321)
> ...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xmlbeans.apache.org
For additional commands, e-mail: dev-h...@xmlbeans.apache.org
