W3C home > Mailing lists > Public > www-dom-ts@w3.org > November 2001

Re: Integrating the DOM test suite in the Batik test infrastructure

From: Vincent Hardy <vincent.hardy@sun.com>
Date: Thu, 29 Nov 2001 09:15:16 +0100
Message-ID: <3C05EE94.DB7C7676@sun.com>
To: Philippe Le Hegaret <plh@w3.org>
CC: Curt Arnold <carnold@houston.rr.com>, www-dom-ts@w3.org
Curt, Dimitri, Philippe,

Thanks for your answers. I think the situation is:

a. You do have a notion of test adapter for the java tests and this 
   should ease the integration into Batik's test infrastructure.

b. The tests currently rely on JAXP and Batik is not using JAXP.

We'll wait until Philippe has the two alternate methods in place
to do the integration into the Batik test suite. In the meanwhile,
we'll have a look at the adapters, as Curt suggested.


Philippe Le Hegaret wrote:
> Curt Arnold wrote:
> > Philippe Le Hegaret was looking at testing Batik using the existing
> > JUnit/Avalon adapters by using the DOM 3 Load/Save interfaces.
> Batik doesn't support the JAXP API and this is currently required to run
> the DOM Test Suite. I'm working on improving the bootstrapping problem
> in the DOM Test Suite in order to support DOM Level 3 LS, JAXP, and do
> the loading ourself. Batik doesn't support DOM Level 3 LS (yet?) so will
> rely on the third solution in order to run the tests.
> Loading the Document ourself requires to have a SAX2 parser but we can include
> the xerces parser in the distribution. Once this loader is ok, I'll change
> the DOMTestCase load method to remove its dependency with JAXP and will change
> accordingly the framework bootstraps. Hopefully, I should have something stable
> before the end of next week.
> Philippe
Received on Thursday, 29 November 2001 03:13:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:04 UTC