You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by bu...@apache.org on 2003/04/18 00:02:22 UTC

DO NOT REPLY [Bug 19130] New: - warfile that contain web examples does not work with Tomcat

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

warfile that contain web examples does not work with Tomcat

           Summary: warfile that contain web examples does not work with
                    Tomcat
           Product: XalanJ2
           Version: 2.5
          Platform: Other
               URL: http://xmlc.enhydra.org/project/mailingLists/xmlc/msg019
                    54.html
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Xalan
        AssignedTo: xalan-dev@xml.apache.org
        ReportedBy: bill-jenkins@attbi.com


Please see the above url.  I know nothing as to validity of the above url, but 
it worked for me.  If the war file does not work which contain the jar files 
under WEB-INF/lib, then that sounds like a bug to me.  Either Tomcat is 
noncompliant or the jar files are.

-----quoted from url-------
Looks like you are using Tomcat.  Here are instructions for Tomcat-4.1.12 
(latest release version), you can do one of two things:

1.  Put Xerces that comes with XMLC-2.1 in CATALINA_HOME/shared/lib.  This 
should work even if you have a newer Xerces version (2.x.x) in common/endorsed.
2.  Put Xerces that comes with XMLC-2.1 in common/endorsed and remove the 
existing Xerces version

Note that you shouldn't put Xerces in WEB-INF/lib.  You end up getting weird 
classloader behavior.  Normally what happens in classloaders is that the XML 
parser highest in the classloader tree (a parent classloader) is used.  Only if 
it isn't found does it use a child classloader.  This behavior is slightly 
different for webapps where the webapp, preferentially, loads libraries from 
the child classloader (the WebappClassloader).  But when the server and the 
webapp are using different XML parsers, things get a bit hairy and you end up 
with weird exceptions.  There were bugs on Tomcat about this and they made it 
so Tomcat won't allow a webapp to override the XML parser when one is put in 
WEB-INF/lib.  This is special behavior for dealing with the problem of XML 
parsers...especially since j2sdk1.4.x now contains an XML parser.  The same 
goes for DOM libraries.

If you want, you can keep gnu-regexp.jar, jtidy.jar and xmlc.jar in WEB-INF/lib 
or put them in shared/lib.  Whichever you want.

---------end quote from url--------------