> Actually I think I disagree. Users have three chances to override the
> defaults; application developers have effectively two.
> So there are plenty of ways to override this default setting. I'd
> almost argue that I'd like to see Sun's RI builds explicitly set this,
> since those bui
you Isaac Shabtay wrote
> jaxp.jar contains an implementation of
> javax.xml.parsers.DocumentBuilderFactory. This implementation's
> "newInstance" method does the search using the four steps above. When
it
> comes to step number 4, it looks for Crimson.
>
> So, if tomorrow there'll be an
Isaac Shabtay wrote:
>
> > Huh? I'm not sure what you mean. The JAXP specification is effectively
> > a bunch of interfaces that anyone can implement (along with the rest of
> > the docs, etc.). Apache happens to have several implementations of
>
> Well, this I already know.
> Yet, javax.xml.p
> Huh? I'm not sure what you mean. The JAXP specification is effectively
> a bunch of interfaces that anyone can implement (along with the rest of
> the docs, etc.). Apache happens to have several implementations of
Well, this I already know.
Yet, javax.xml.parsers.DocumentBuilderFactory and
ja
Isaac Shabtay wrote:
>
> Hi,
>
> javax.xml.parsers.DocumentBuilderFactory is supposed to search for the
> factory implementation in some places.
> The last place to look for is:
>
> = START QUOTE ==
> • Platform default DocumentBuilderFactory instance.
>
> = END QUOTE =
Shane Curcuru wrote:
>
> like this. Sun then happend to choose to re-ship their own versions of
> Crimson and Xalan as the 'reference implementations' of the actual JAXP
> 1.1 release - which is actually pretty cool that they chose our
> implementations over other ones.
One orthogonal comment h
Huh? I'm not sure what you mean. The JAXP specification is effectively
a bunch of interfaces that anyone can implement (along with the rest of
the docs, etc.). Apache happens to have several implementations of
JAXP 1.1: Crimson, Xerces 1.x, Xerces 2.x, and Xalan 2.x - because we
already had the
