W3C home > Mailing lists > Public > www-dom-ts@w3.org > January 2002

Re: Release preparation (need other eyes on classloader issue)

From: Dimitris Dimitriadis <dimitris@ontologicon.com>
Date: Tue, 29 Jan 2002 13:34:52 +0100
Cc: <www-dom-ts@w3.org>
To: "Curt Arnold" <carnold@houston.rr.com>
Message-Id: <97A4CE44-14B4-11D6-B535-000393556882@ontologicon.com>
Java isn't my strongest side; I've tried to get some information about 
this without success. As Curt says, if someone can invest some time into 
this it would be great as it woul simplify the task of running tests for 
particular implementations.


On Tuesday, January 29, 2002, at 07:52 , Curt Arnold wrote:

> I've updated build.xml to download the new DOM 3 Core and AS/LS working 
> drafts and moved the .patch files into a patches directory.
> I spent some time trying to get the test suite runnable from the JUnit 
> GUI test runners.  Unfortunately, I'm running into ClassNotFound at run 
> time.  If any of you are masters of the Java class loaders and can 
> diagnose the situation, I would appreciate it.
> The idea is that you would be able to do something like:
> java -jar junit-run.jar
> and would be able to select a TestSuite for the spec, parser and 
> configuration that interests you.  (Only 
> org.w3c.domts.level1.core.TestDefaultParser is implemented now, but 
> would expect to have many similar classes if we can get this working)
> However, if you just do that, you will get a ClassNotFound error for 
> DOMTestSink which should have automatically been on the classpath from 
> the junit-run manifest (in dom1-core.jar)
> I also updated the snapshoted documentcreatecdatasection.java to remove 
> the .xml extension.  Generating that test would typically break Xalan, 
> so a version prepared by Saxon is copied instead.  But I hadn't updated 
> the copy since the media type changes.
Received on Tuesday, 29 January 2002 07:34:49 UTC

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