SV: [jdom-interest] One less TODO item
pernorrman at telia.com
Tue Oct 7 08:34:13 PDT 2003
I thought it was the SAXParsers (or XMLReader) that resolved
the relative URI. If I supply an EntityResolver to either
crimson or xerces, the system id is already resolved when
the callback is made. How do you work around that in XOM?
Or does it have its own parser?
> -----Ursprungligt meddelande-----
> Från: Elliotte Rusty Harold [mailto:elharo at metalab.unc.edu]
> Skickat: den 7 oktober 2003 16:19
> Till: Per Norrman; jdom-interest at jdom.org
> Ämne: Re: [jdom-interest] One less TODO item
> At 12:26 PM +0200 10/7/03, Per Norrman wrote:
> >This is *not* a JDOM bug. It is the SAXParser's responsibility to
> >resolve the system identifier and create the input source.
> This seems
> >to be a dark area where magic is necessary, crimson and
> xerces does it
> >differently, and at least crimson gets it wrong.
> It's not JDOM's fault, but it is something JDOM needs to work around.
> XOM successfully works around it for the case of pathless URLs like
> However, I have not yet devised a workaround that can handle URLs
> like http://www.ibiblio.org/xml where /xml might be a directory and
> might be a filename, and you really have to ask the server to find
> out which. :-(
> Elliotte Rusty Harold
> elharo at metalab.unc.edu
> Processing XML with Java (Addison-Wesley, 2002)
More information about the jdom-interest