Saxon

Legacy ID: #4791786 Legacy Poster: Michael Kay (mhkay)

At compile time, if you don't want JDOM (say) then you should be able to leave package net.sf.saxon.jdom out of the compilation. At run time, with the standard build, if you don't want JDOM then neither the jdom.jar nor the saxon9-jdom.jar needs to be on the classpath. I hope that answers the question. Michael Kay

Legacy ID: #4791809 Legacy Poster: Peter B. West (pbw)

Thanks Michael. If I do want JDOM, do both need to be on the classpath? Do I need one of the pairs - jdom or xom or dom4j - in my classpath, or can saxon run happily with none of the above? In the latter case, what am I unable to do? (A reference to a document may be what I need here.) Peter

Legacy ID: #4791835 Legacy Poster: Michael Kay (mhkay)

If you want to use JDOM, then both jdom.jar and saxon9-jdom.jar need to be on the classpath. You only need the jar-pairs for the object models that you want to use; it's fine to run with none of them on the classpath (I do, most of the time). Michael Kay

Legacy ID: #4791854 Legacy Poster: Peter B. West (pbw)

Thanks again. I recently bought the 2.0 books, and I am finding them, and saxon, extremely useful. Peter