You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/02/21 23:11:52 UTC

DO NOT REPLY [Bug 6628] New: - Can't specify application specific XML parsers

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=6628>.
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=6628

Can't specify application specific XML parsers

           Summary: Can't specify application specific XML parsers
           Product: Tomcat 4
           Version: 4.0.2 Final
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: toby@reyelts.com


In org.apache.catalina.loader.WebappClassloader there are a set of 
defined "triggers" which prevent certain classes from being loaded:

private static final String[] classTriggers = {
        "javax.net.",                                // JSSE      added in 1.4
        "javax.security.cert.",                      // JSSE      added in 1.4
        "javax.naming.",                             // JNDI      added in 1.3
        "javax.xml.",                                // JAXP      added in 1.4
        "org.xml.sax.",
        "org.w3c.dom."
    };

You'll notice that all of the xml parsing packages are specified in this 
trigger list. This means that Tomcat refuses to load any XML parser which may 
have been placed in WEB-INF/lib folders. This makes it impossible to 
specify "per-application" XML parsers, unless you load the XML classes yourself.

God bless,
-Toby

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>