W3C home > Mailing lists > Public > www-dom-ts@w3.org > July 2007

Re: build problem caused by xmlns validation

From: Hallvord R. M. Steen <hallvord@opera.com>
Date: Tue, 03 Jul 2007 11:41:01 +0200
To: "Curt Arnold" <carnold@houston.rr.com>, www-dom-ts@w3.org
Message-ID: <op.tuvuinr9a3v5gv@hr-opera.oslo.opera.com>

On Sat, 30 Jun 2007 06:55:03 +0200, Curt Arnold <carnold@houston.rr.com>  
wrote:

>> ant dom2-core-gen-jsunit
>>
>> fails with this error message:
>> The prefix "xml" cannot be bound to any namespace other than its usual  
>> namespace; neither can the namespace for "xml" be bound to any prefix  
>> other than "xml".
<X>
>> Caused by the xmlns:ns0 in demo code like the following:
>>
>> <p>Returns the UTF-32 offset corresponding to a UTF-16 offset. Used for  
>> random access. To find the UTF-32 length of a string, use:<eg  
>> xmlns:ns0="http://www.w3.org/XML/1998/namespace"  
>> ns0:space="preserve">len32 = findOffset32(source, source.length());</eg>

> The constraint that the XML namespace URL not be bound to a different  
> prefix was not in the original 1999 XML Namespaces recommendation but  
> was added in an errata (http://www.w3.org/XML/xml-names-19990114- 
> errata#NE05, date uncertain) and is in the recent second edition.

Right, so the spec contains sample code that is made invalid by an errata  
:-(

> The issue could be avoided by using an earlier XML parser, either using  
> Ant 1.6.5 or JDK 1.4 or a combination should avoid the issue.  The test  
> suites had been built nightly on Apache Gump until recently when it was  
> removed due to capacity constraints and I do not recall this issue  
> appearing.   It would be great if you could identify more of your build  
> environment particularly the default JAXP parser, so I don't have to  
> hunt for a configuration that runs into the problem.

I've got Ant 1.7.0, I'm not entirely sure where to find other relevant  
version information but there is a file called libraries.properties where  
these entries look relevant:

xerces.version=2.8.1
xercesImpl.version=${xerces.version}
#should be in sync w/ xerces, but not in the maven repository
#xmlParserAPIs.version=${xerces.version}
xmlParserAPIs.version=2.6.1
xalan.version=2.7.0
xml-resolver.version=1.1

Is that what you need?

-- 
Hallvord R. M. Steen
Core QA JavaScript tester, Opera Software
http://www.opera.com/
Opera - simply the best Internet experience
Received on Tuesday, 3 July 2007 09:38:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 April 2009 12:58:50 GMT