XOM API for Processing XML with Java

[Steve Loughran <steve.loughran AT gmail.com>]

On Apr 7, 2005 11:01 PM, Elliotte Rusty Harold <elharo AT metalab.unc.edu> wrote:
> I have now turned off internal DTD subset building when parsing with
> Crimson and when there's an external DTD subset. It's an extreme
> solution but so far I haven't thought of anything better. :-(

abandoning crimson support ?

You can also set up gump to test against Crimson, as we do for ant,
even though crimson is not supported, some tests are explicitly
excluded (*) and all defects file against are WONTFIX:
http://brutus.apache.org/gump/public/ant/test-ant-no-xerces/index.html

The purpose of that test is actually to make sure that there are no
xerces-only features creeping in, rather than verify that crimson
works properly.

On the subject of gump, Xom is failing:
  http://brutus.apache.org/gump/public/xom/xom/gump_work/build_xom_xom.html
Do you want/need some changes to your config there, to track what you
are up to in Jaxen?

-Steve


(*) Ant1.7 has a condition that checks the hosting XML parser for
functionality used to make sure there is no attempt to run
<schemavalidate> on crimson
<or>
  <parsersupports
    feature="http://apache.org/xml/features/validation/schema"/>
  <parsersupports
    feature="http://java.sun.com/xml/jaxp/properties/schemaSource"/>
</or>