[
Lists Home |
Date Index |
Thread Index
]
/ Elliotte Rusty Harold <elharo@metalab.unc.edu> was heard to say:
| At 11:03 AM -0500 1/23/02, Norman Walsh wrote:
|
|>I maintain that adding a resolveURI(uri, baseURI) method to the SAX
|>API is "the right thing".
|>
|
| While this is important I just can't see any reason to put this in SAX
| instead of in java.net. In fact, I think this constructor probably
Yeah, well, getting SAX updated is probably slightly easier than
getting java.net changed :-)
| offers exactly the functionality you're looking for:
|
| public URL(URL context,
| String spec)
| throws MalformedURLException
Uhm. I'm confused. That'll return the stream, but I actually want the
URI to be passed through *the resolver* (for example XML Catalogs[1])
not blindly slurped across the net.
I want an entry point to do for URIs what resolveEntity() does for
external identifiers. And I maintain that calling a URI a system
identifier with a null public identifier is wrong.
Be seeing you,
norm
[1] http://www.oasis-open.org/committees/entity/spec.html
--
Norman.Walsh@Sun.COM | One stops being a child when one realizes that
XML Standards Engineer | telling one's trouble does not make it
XML Technology Center | better.--Cesare Pavese
Sun Microsystems, Inc. |
|
