Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (herse.apache.org: domain of t.p.ellison@gmail.com
 designates 66.249.92.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding;
        b=gJSTdS5hwSVYcod1ogeNyk/TWfnV8dResUN4MUVzDT1N4fOXcCOkEw0c40s7AEixkUQVRv8YE73ZhB8yUaLcWvRxErPPlTFb42UHaCdP+awBpqbXcXO3uIyuy51owm/iKkVAHmV0KUReXm7Z8CYX53qzgerkGipGBpeVQ8o5aIM=
Message-ID: <458AA147.3040702@gmail.com>
Date: Thu, 21 Dec 2006 14:59:19 +0000
From: Tim Ellison <t.p.ellison@gmail.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: dev@harmony.apache.org
Subject: Re: [classlib][xml] Update version of Xerces
References: <45880EE0.7000300@gmail.com>
 <3b3f27c60612202126y1b8d42ebwc30d80f79a94d36d@mail.gmail.com>
In-Reply-To: <3b3f27c60612202126y1b8d42ebwc30d80f79a94d36d@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Nathan Beyer wrote:
> There are new XML Commons that are needed for 2.9.0 (xml-apis). As an
> aside to this, the XML Commons code probably needs to be pulled out of
> our "xerces" OSGi module, as it's common to both "xerces" and "xalan".
> 
> BTW - I've been attempting to help the Xerces team upload the latest
> JARs to the Maven central repo (repo1.maven.org), but that's not
> moving along very quickly. I'm just mentioning this if you can't find
> the JARs on those servers.

Ack -- thanks for the note.  I'm pulling down the Xerces binary JAR from
the Apache servers and extracting the xml-apis, xercesImpl, and resolver
JARs at the moment.  However, I've not been able to figure out the cause
of a consistent failure I see locally in the Harmony test suites after
upgrading.  It doesn't help that there is no debug info in the Xerces
class files, and when I recompile the problem seems to go away (or at
least be intermittent).  I've also failed to reproduce on simpler tests.

I suspect that we have fouled earlier and this is a downstream failure,
but I haven't been able to track it down.  FYI here's the stacktrace:

java.lang.NullPointerException
org.apache.xerces.dom.NamedNodeMapImpl.findNamePoint(Unknown Source)
org.apache.xerces.dom.AttributeMap.setNamedItem(Unknown Source)
org.apache.xerces.dom.DeferredElementImpl.synchronizeData(Unknown Source)
org.apache.xerces.dom.ElementImpl.getTagName(Unknown Source)
org.apache.xerces.dom.DeepNodeListImpl.nextMatchingElementAfter(Unknown
Source)
org.apache.xerces.dom.DeepNodeListImpl.item(Unknown Source)
org.apache.xerces.dom.DeepNodeListImpl.getLength(Unknown Source)
java.util.Properties.loadFromXML(Properties.java:566)
tests.api.java.util.PropertiesTest.test_storeToXMLLjava_io_OutputStreamLjava_lang_StringLjava_lang_String(PropertiesTest.java:398)
java.lang.reflect.AccessibleObject.invokeV(AccessibleObject.java:25)


Regards,
Tim