[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Classpathx-xml] Inconsistency in EntityResolvers?

From: Egon Willighagen
Subject: [Classpathx-xml] Inconsistency in EntityResolvers?
Date: Sun, 7 Apr 2002 18:36:56 +0200

Hi all,

on 2 Feb. I posted a question about SYSTEM identifiers in which
the protocol was missing... The problem is solved now, but I have one more 
question about it.

When not validating and using EntityResolver I got that missing-protocol 
exception about which I wrote back then. It was solved by setting a kind of 
root URL for the main document. The problem occured when other files were
included by means of SYSTEM entities, but also when referencing to DTDs like
in <!DOCTYPE blabla SYSTEM "blabla.dtd">.

However, someone pointed to me to a workaround that used EntityResolver2
instead... It seems that this resolver does not expand (or absolutize the URL)
befour trying to validate, as EntityResolver itself does, even without 
validation. Thus, the two classes do not behave consistently for the same XML 
document. Is this intentionally? If so, why the difference? And why does 
EntityResolver tries to sanitize the SYSTEM id in the DOCTYPE line even when 
it does not validate anyway?

I hope someone can clarify this.

Looking forward to hearing from someone,

kind regards,

Egon Willighagen

reply via email to

[Prev in Thread] Current Thread [Next in Thread]