On Thu, 31 Jan 2008 11:12:28 -0800, Greg R. Broderick
It is worth noting that distributing with Xerces would not break WORA.
Sure. But it _would_ break my other goal of not having to distribute
additional components with my application.
Xerces is distributed as part of the JRE 1.5, so you don't need to
any additional components.
I'm afraid I don't have the time to research this myself, and
unfortunately I'm getting mixed signals here. Arne's reply implies that
while Xerces is "by far the most widely used JAXP implementation", that
does not mean that all Java implementations use it. Arne's suggestion
that he's got 68 versions of it on his hard disk implies to me that it's
not part of the implementation (why would people deliver it as an add-on
if it were?).
On the other hand, you say (or at least imply) that _all_ 1.5
implementations will have Xerces. Is this fact documented somewhere
official? Or is it just something that's "common knowledge"?
In any case, I appear to have a solution that isn't dependent on the
implementation (which frankly, I feel should always be a goal in Java
development -- even though the environment has strengths other than
that, certainly it's my feeling that's one of the greatest ones). So
it's somewhat of a moot point. But if you have some official source
that clearly documents whether a specific implementation can be assumed,
I'm all ears.
org.xml.sax package) *is* the guarantee that they're part of the language.
You may relax.