[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: SAX Locator vs {start,end}Entity

• To: <xml-dev@l...>
• Subject: Re: SAX Locator vs {start,end}Entity
• From: "Karl Waclawek" <karl@w...>
• Date: Thu, 20 Feb 2003 09:34:18 -0500
• References: <200302201249.MAA24112@m...>

> >The SAX 2.0 API documentation is silent on this, but the method
> >descriptions in org.xml.sax.Locator have always led me to believe that the
> >location should be the entity in which the reference was encountered,
> 
> Xerces seems to disagree: it returns the entity whose start or end is
> being reported.  So I guess one can't rely on it.

I think that is what Gregory meant.
It would surprsie me to find a SAX parser that does it differently.
 
> But it's worse: the reason I'm doing this is to determine the current
> base URI, taking account of entity boundaries and xml:base.  This
> seems to be impossible, since the locator returns the system ID of
> the entity, not its URI.  So if there is http redirection (e.g. a
> directory referred to without its trailing slash) the locator provides
> the unredirected value.  As far as I can see, it's impossible to
> calculate the base URI using SAX.

> Are there any plans to directly support base URIs in a future version
> of SAX?

In SAX2 extensions the EntityResolver2 interface has an "upgraded"
version of resolveEntity() which passes the baseURI.

Karl

• Follow-Ups:
  • Re: SAX Locator vs {start,end}Entity
    • From: Richard Tobin <richard@c...>

• References:
  • Re: SAX Locator vs {start,end}Entity
    • From: Richard Tobin <richard@c...>

• Prev by Date: Re: SAX Locator vs {start,end}Entity
• Next by Date: data input to an XSL produced page -- best practices
• Previous by thread: Re: SAX Locator vs {start,end}Entity
• Next by thread: Re: SAX Locator vs {start,end}Entity
• Index(es):
  • Date
  • Thread