DO NOT REPLY [Bug 4931] New: - Parser does not consistently resolve relatice DTD paths

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4931>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4931

Parser does not consistently resolve relatice DTD paths

           Summary: Parser does not consistently resolve relatice DTD paths
           Product: Xerces-J
           Version: 1.4.3
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Other
        AssignedTo: xerces-j-dev@xml.apache.org
        ReportedBy: flawlor@athensgroup.com


I have xml files with the DTD spec:
<!DOCTYPE links SYSTEM "../Links.dtd">
That is, the dtd for all these files is
in their parent directory.

This is in a web application run by
Tomcat 4.0 (Catalina).  If I put the 
xerces.jar in webapps/myapp/WEB-INF/lib
it works fine.  However, Catalina currently
has a security bug that prevents me from
putting it there (xerces gets security
exceptions trying to access the files).

But, since this is a shared lib it makes
sense anyway to put it in common/lib.
However, when I put it there, it interprets
the relative DTD path as relative to 
whatever directory Catalina is run in!

This is unworkable from a web app developer's
point of view.  There might be multiple 
reasonable interpretations of a relative DTD
path, but from a developer's viewpoint there
are some essential elements:

1) It needs to be consistent regardless of 
where xerces.jar is loaded from
2) It cannot require the developer to specify
a relative path that makes any assumption 
about where Tomcat is installed or the name
of the web app main directory (since these
vary from install to install and are not
under developer control).

Craig R. McClanahan [craigmcc@apache.org]
from Tomcat says that this is a xerces bug,
not Tomcat.

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org