XOM API for Processing XML with Java

[luca passani <passani AT eunet.no>]

Elliotte, I suspect you have removed too much stuff. My WURFL api still 
builds, but
unit tests fail:

C:\projects\wurfl\antbuild>ant runtest
Buildfile: build.xml

prepare:

compileapi:

compiletags:

buildlib:

compiletest:

runtest:
    [java] .Starting :Mon Jun 02 13:05:11 CEST 2003
    [java] setUp() capability matrix and UA Manager
    [java] E.Starting :Mon Jun 02 13:05:11 CEST 2003
    [java] setUp() capability matrix and UA Manager
    [java] E
    [java] Time: 0.18
    [java] There were 2 errors:
    [java] 1) 
testUARetrieval(StandAlone)java.lang.NoClassDefFoundError: nu/xom
/ParseException
    [java]     at 
net.sourceforge.wurfl.wurflapi.ObjectsManager.getUAManagerIns
tance(Unknown Source)
    [java]     at StandAlone.setUp(Unknown Source)
    [java]     at StandAlone.main(Unknown Source)
    [java] 2) 
testUARetrievealLoose(StandAlone)java.lang.NoClassDefFoundError:
nu/xom/ParseException
    [java]     at 
net.sourceforge.wurfl.wurflapi.ObjectsManager.getUAManagerIns
tance(Unknown Source)
    [java]     at StandAlone.setUp(Unknown Source)
    [java]     at StandAlone.main(Unknown Source)

    [java] FAILURES!!!
    [java] Tests run: 2,  Failures: 0,  Errors: 2


BUILD SUCCESSFUL
Total time: 3 seconds
----------------------------------------------------------

Here is what happens after I roll back to version 1.0d15
(everything goes smooth)

C:\projects\wurfl\antbuild>ant runtest
Buildfile: build.xml

prepare:

compileapi:

compiletags:

buildlib:

compiletest:

runtest:
    [java] .Starting :Mon Jun 02 13:07:42 CEST 2003
    [java] setUp() capability matrix and UA Manager
    [java] wurfl.properties file found. Lemme have a look...
    [java] using file://C:\projects\wurfl\antbuild\resources\wurfl.xml 
file fou
nd in wurfl.properties
    [java] Testing UA Retrieval
    [java] 1 -> test caching for device ID retrieval from UA
    [java] 2 -> test for correctness
    [java] .Starting :Mon Jun 02 13:07:44 CEST 2003
    [java] setUp() capability matrix and UA Manager
    [java] 1 -> test caching for device ID retrieval from UA (loose)

    [java] Time: 2.574

    [java] OK (2 tests)


BUILD SUCCESSFUL
Total time: 5 seconds
C:\projects\wurfl\antbuild>

Elliotte Rusty Harold wrote:

> I've posted version 1.0d16 of XOM in the usual location:
>
> http://www.cafeconleche.org/XOM/
>
> The primary focus of this release is adding unit tests for XSLT, and 
> fixing the bugs they uncovered:
>
>     * More accurate exception messages from the XSLTransform constructors
>     * XSLT unit tests
>     * The distribution now includes Michael Kay's SAXON jar archive so
>       that XSLT works with Java 1.2 and 1.3 VMs.
>     * Fixed a nasty bug in Element.toXML that was making XSLT
>       transforms fail when elements were in the default namespace
>     * You can now transform a NodeList as well as a complete document
>
> Other assorted improvements in this release include:
>
>     * The standard jar file no longer includes the samples, tests, and
>        benchmarks packages. You can compile these from source if you
>        need them, but omitting them makes the jar file smaller for
>       developers who want to bundle XOM with their own applications.
>     * The jar file is indexed to improve class loading speed.
>     * I moved SAXConverter and DOMConverter out of the core package
>       into a new nu.xom.converters package. They're fairly special 
> purpose.
>     * Improved compatibility with Java 1.2.
>     * SAX filters can no longer bypass well-formedness checks
>     * Worked around a Xerces and Crimson bug that inhibits relative URL
>       resolution from pathless base URLs such as 
> http://www.cafeconleche.org
>     * The FibonacciSOAPClient sample program works now
>     * Document.insertChild(DocType, position) now throws an
>       IllegalAddException if the Document already has a DocType,
>       rather than silently replacing it.
>
> Other than the new XSLTransform.transform(NodeList) method and the new 
> nu.xom.converters package for SAXConverter and DOMConverter, there are 
> no API level changes in this release. Most code that ran with 1.0d15 
> should run unchanged with 1.0d16 .