On Wednesday, 01/05/2005 at 02:43 PST, Bob Foster <[EMAIL PROTECTED]> wrote:
> > If we're doing our own URI support... why?
> Why what?
"Why are we doing so". Sorry, I thought that was self-evident from context.
I agree I should have been clearer, especially since not all the
participants here
Why what? I can deal with top-quoting, but no-quoting is a challenge. ;-}
Bob Foster
Joseph Kesselman wrote:
If we're using the Java URI support, I believe the jar: scheme is supported
by that layer. If we're doing our own URI support... why?
__
Joe Kesselman, IB
My apologies. I'm just in a snippy mood today. And sloppy, too. I
thought you _were_ the original asker. Sorry.
I almost never use the feature, but I'm pretty sure Java can resolve
jar: URIs. The jar: URI is a Sun invention.
Bob
Eric J. Schwarzenbach wrote:
My pointing the asker to EntityResolv
If we're using the Java URI support, I believe the jar: scheme is supported
by that layer. If we're doing our own URI support... why?
__
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"The world changed profoundly and unpredictably t
My pointing the asker to EntityResolver wasn't meant to insult your
knowledge.
My wording was "I'm not aware"; if, despite my unawareness, a jar:
scheme really is supported, then my apologies for muddling the issue.
Cheers,
Eric
Bob Foster wrote:
I know about EntityResolver, thanks. What makes
I know about EntityResolver, thanks. What makes you think a jar: URI
isn't a resolvable URI? I guess the answer to my question is no.
Bob Foster
Eric J. Schwarzenbach wrote:
I've never used the external-schemaLocation (or
external-noNamespaceSchemaLocation) property, so maybe I'm reading the
do
Does this question have anything to do with Xerces?
I would expect a query string in a jar: URI to cause problems. To form a
URI out of a base URI and a relative URI, the query string and/or
fragment identifier should be stripped, the URI truncated at the final /
and the relative URI processed (
I've never used the external-schemaLocation (or
external-noNamespaceSchemaLocation) property, so maybe I'm reading the
documentation wrong, but doesn't the value you are setting for the
schema location need to be a resolvable URI? I'm not aware that the
parser knows by default how to find a fi
Michael,
You guessed right. I can get to to run now.
Thanks.
Peter
Michael Glavassevich wrote:
Hello Peter,
I'm guessing you got this code from the documentation. The sample code got
out of synch with changes to DOM Level 3. The "LS-Load" feature was
renamed "LS" in one of the working drafts. It
Hello Peter,
I'm guessing you got this code from the documentation. The sample code got
out of synch with changes to DOM Level 3. The "LS-Load" feature was
renamed "LS" in one of the working drafts. It docs were fixed in CVS but
not on the website. I've just updated them there [1].
Thanks.
[1
Title: Xerces URI does not handle JAR scheme?
I have an application that loads resources from an embedded zip file. This is done via a protocol handler, so the following URI is obtained:
jar:embeddedzipfile:file:/home/cprowse/data.zip?lib/config.jar!/repository.xml
Which follows the no
11 matches
Mail list logo