Re: parse error in application web.xml under 5.0.24 but not 5.0.19
The problem was my webapps needed to have the 'privileged' attribute set to true on the Context tag. Reading the doc on the privileged attribute on the Context tag, it says Set to true to allow this context to use container servlets, like the manager servlet. I've been unable to find any additional information on container servlets in the Servlet Spec, and searching the source code didn't lead to any insight. Which leads me to three questions: 1) What is a container servlet? 2) How does Tomcat determine that my webapp is a container servlet? 3) Why didn't I need to set the privileged attribute in 5.0.19? Thanks, Jim Jim Hopp wrote: I've just upgraded from 5.0.19 to 5.0.24. My webapps worked fine under 5.0.19, but Tomcat is throwing the exception below under 5.0.24 when it tries to start the webapp. (The apps also start properly under 5.0.20, but fail under 5.0.21 with the same exception so it appears that a change made in 5.0.21 is causing the problem.) My server.xml and web.xml follow the exception trace. May 10, 2004 3:33:30 PM org.apache.catalina.core.StandardContext start FINE: Starting tomcat.localhost./property.Context May 10, 2004 3:33:30 PM org.apache.catalina.core.StandardContext createObjectNam e FINE: Registering j2eeType=WebModule,name=//localhost/property,J2EEApplication=n one,J2EEServer=none for null May 10, 2004 3:33:30 PM org.apache.catalina.core.StandardContext start FINE: Configuring default Resources May 10, 2004 3:33:30 PM org.apache.catalina.core.StandardContext start FINE: No realm for this host directory:type=Host,host=localhost,path=/property May 10, 2004 3:33:30 PM org.apache.catalina.core.StandardContext start FINE: Configuring non-privileged default Loader May 10, 2004 3:33:30 PM org.apache.catalina.core.StandardContext start FINE: Processing standard container startup May 10, 2004 3:33:31 PM org.apache.catalina.core.StandardContext setPublicId FINE: Setting deployment descriptor public ID to '-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN' May 10, 2004 3:33:31 PM org.apache.commons.digester.Digester endElement SEVERE: End event threw exception java.lang.ClassNotFoundException: org.apache.catalina.Container at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa der.java:1340) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoa der.java:1189) at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:243) at org.apache.commons.digester.Rule.end(Rule.java:276) at org.apache.commons.digester.Digester.endElement(Digester.java:1058) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source ) at org.apache.xerces.impl.dtd.XMLDTDValidator.endNamespaceScope(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown S ource) at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement( Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent Dispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un known Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.digester.Digester.parse(Digester.java:1548) at org.apache.catalina.startup.ContextConfig.applicationConfig(ContextCo nfig.java:263) at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:62 4) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfi g.java:216) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lifecycl eSupport.java:119) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4 268) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) at org.apache.catalina.core.StandardHost.start(StandardHost.java:789) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1083) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:478 ) at org.apache.catalina.core.StandardService.start(StandardService.java:4 76) at org.apache.catalina.core.StandardServer.start(StandardServer.java:229 8) at org.apache.catalina.startup.Catalina.start(Catalina.java:556) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at
RE: parse error in application web.xml under 5.0.24 but not 5.0.19
you might have done this already, but according to the changelog... http://jakarta.apache.org/tomcat/tomcat-5.0-doc/changelog.html there were a number of fixes/enhanements in and around XML processing of web/server.xml files. And in 5.0.22, a different version of xerces. That may not help at all, but it gives you a start on 'what changed'. -Original Message- From: Jim Hopp [mailto:[EMAIL PROTECTED] Sent: Monday, May 10, 2004 5:59 PM To: [EMAIL PROTECTED] Subject: parse error in application web.xml under 5.0.24 but not 5.0.19 I've just upgraded from 5.0.19 to 5.0.24. My webapps worked fine under 5.0.19, but Tomcat is throwing the exception below under 5.0.24 when it tries to start the webapp. (The apps also start properly under 5.0.20, but fail under 5.0.21 with the same exception so it appears that a change made in 5.0.21 is causing the problem.) My server.xml and web.xml follow the exception trace. snip / - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Parse error in application web.xml (addChild: Child name 'jsp' is not unique)
Howdy, Did you comment out the jsp servlet definition in $CATALINA_HOME/conf/web.xml? You can only have one servlet with that name jsp. The above is the global web.xml which is read in addition to your application's web.xml. Most people simply leave the JSP servlet definition in the global web.xml and don't add it to their own webapp's web.xml. Yoav Shapira Millennium ChemInformatics -Original Message- From: Shailesh Modi [mailto:[EMAIL PROTECTED] Sent: Monday, September 08, 2003 5:42 AM To: [EMAIL PROTECTED] Apache. Org (E-mail) Subject: Parse error in application web.xml (addChild: Child name 'jsp' is not unique) Hi, Has somebody got this error ? I am getting this while starting my tomcat 4.1.27 to deploy my web-app and when it reads my web-app's web.xml . Error : 2003-09-08 15:00:54 ContextConfig[/remind/cafe] Parse error in application web.xml java.lang.IllegalArgumentException: addChild: Child name 'jsp' is not unique at org.apache.commons.digester.Digester.createSAXException(Digester.java:2 540) at org.apache.commons.digester.Digester.createSAXException(Digester.java:2 566) at org.apache.commons.digester.Digester.endElement(Digester.java:1061) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.endNamespaceScope(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Un know n Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2190) at org.apache.catalina.startup.Catalina.start(Catalina.java:512) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) 2003-09-08 15:00:54 ContextConfig[/remind/cafe]: Occurred at line 60 column 13 2003-09-08 15:00:54 ContextConfig[/remind/cafe]: Marking this application unavailable due to previous error(s) I looked in my web.xml at line 60, where i have specified 'jsp' servlet definition. servlet servlet-namejsp/servlet-name servlet-classorg.apache.jasper.servlet.JspServlet/servlet-class /servlet Am i doing something wrong in migrating from tomcat 3 to 4.1.27 . ? Thanks a lot Shailesh Modi This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parse error in application web.xml (addChild: Child name 'jsp' is not unique)
I always thought (or at least the docs have said) that one can override the default servlet. The same should be true with the jsp servlet too. -Tim Shapira, Yoav wrote: Howdy, Did you comment out the jsp servlet definition in $CATALINA_HOME/conf/web.xml? You can only have one servlet with that name jsp. The above is the global web.xml which is read in addition to your application's web.xml. Most people simply leave the JSP servlet definition in the global web.xml and don't add it to their own webapp's web.xml. Yoav Shapira Millennium ChemInformatics - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Parse error in application web.xml (addChild: Child name 'jsp' is not unique)
It worked when i removed the jsp servlet definition from my web-app web.xml but when i tried commenting jsp servlet definition in $CATALINA_HOME/conf/web.xml and kept that in my web.xml only. It gave me errors as 2003-09-08 19:06:30 ContextConfig[/remind/cafe] Parse error in default web.xml java.lang.IllegalArgumentException: Servlet mapping specifies an unknown servlet name jsp because somehow it doesnt load jsp servlet from any other web app's web.xml definition and there were other web-apps too which didnt have their own web.xml. So i didnt touch the tomcat's web.xml and removed the specification from my web.xml Yoav , Thanks a lot. Regards, Shailesh -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Monday, September 08, 2003 6:48 PM To: Tomcat Users List; [EMAIL PROTECTED] Subject: RE: Parse error in application web.xml (addChild: Child name 'jsp' is not unique) Howdy, Did you comment out the jsp servlet definition in $CATALINA_HOME/conf/web.xml? You can only have one servlet with that name jsp. The above is the global web.xml which is read in addition to your application's web.xml. Most people simply leave the JSP servlet definition in the global web.xml and don't add it to their own webapp's web.xml. Yoav Shapira Millennium ChemInformatics -Original Message- From: Shailesh Modi [mailto:[EMAIL PROTECTED] Sent: Monday, September 08, 2003 5:42 AM To: [EMAIL PROTECTED] Apache. Org (E-mail) Subject: Parse error in application web.xml (addChild: Child name 'jsp' is not unique) Hi, Has somebody got this error ? I am getting this while starting my tomcat 4.1.27 to deploy my web-app and when it reads my web-app's web.xml . Error : 2003-09-08 15:00:54 ContextConfig[/remind/cafe] Parse error in application web.xml java.lang.IllegalArgumentException: addChild: Child name 'jsp' is not unique at org.apache.commons.digester.Digester.createSAXException(Digester.java:2 540) at org.apache.commons.digester.Digester.createSAXException(Digester.java:2 566) at org.apache.commons.digester.Digester.endElement(Digester.java:1061) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.endNamespaceScope(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.handleEndElement(Unknown Source) at org.apache.xerces.impl.dtd.XMLDTDValidator.endElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Un know n Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2190) at org.apache.catalina.startup.Catalina.start(Catalina.java:512) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) 2003-09-08 15:00:54 ContextConfig[/remind/cafe]: Occurred at line 60 column 13 2003-09-08 15:00:54 ContextConfig[/remind/cafe]: Marking this application unavailable due to previous error(s) I looked in my web.xml at line 60, where i have specified 'jsp' servlet definition. servlet servlet-namejsp/servlet-name servlet-classorg.apache.jasper.servlet.JspServlet/servlet-class /servlet Am i doing something wrong in migrating from tomcat 3 to 4.1.27 . ? Thanks a lot Shailesh Modi This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Parse error in application web.xml (addChild: Child name 'jsp' is not unique)
Howdy, You can override it with whatever you want, just don't use the same servlet-name ;) Servlet names must be unique across both your and the global web.xml. Yoav Shapira Millennium ChemInformatics -Original Message- From: Tim Funk [mailto:[EMAIL PROTECTED] Sent: Monday, September 08, 2003 9:31 AM To: Tomcat Users List Subject: Re: Parse error in application web.xml (addChild: Child name 'jsp' is not unique) I always thought (or at least the docs have said) that one can override the default servlet. The same should be true with the jsp servlet too. -Tim Shapira, Yoav wrote: Howdy, Did you comment out the jsp servlet definition in $CATALINA_HOME/conf/web.xml? You can only have one servlet with that name jsp. The above is the global web.xml which is read in addition to your application's web.xml. Most people simply leave the JSP servlet definition in the global web.xml and don't add it to their own webapp's web.xml. Yoav Shapira Millennium ChemInformatics - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parse error in application web.xml
Carey - Put all servlet tags together and then all servlet-mapping tags together AFTER the servlet tags. Regards, Lajos Lott, Carey wrote: Instead of depending on the invoker servlet, I have added our servlets to the web.xml file inside of the app's WEB-INF directory. However, now I am getting the following error when I try to start tomcat with the changed web.xml: 2003-01-17 13:07:51 ContextConfig[/esd] Parse error in application web.xml org.xml.sax.SAXParseException: The content of element type web-app must match (icon?,display-name?,description?,distributable?,context-param*,filter*,fil ter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mappin g*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,se curity-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-loca l-ref*). I have validated the web.xml file using IE. No errors are apparent. The file displays properly in the browser. Can somebody look at the web.xml, and see what I am missing? I know it has to be something really easy that I am overlooking. Thanks in advance for the Help web.xml file: ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN http://java.sun.com/dtd/web-app_2_3.dtd; web-app welcome-file-list welcome-fileindex.html/welcome-file welcome-fileindex.htm/welcome-file welcome-fileindex.jsp/welcome-file /welcome-file-list !-- Example servlet servlet-nameDateServlet/servlet-name servlet-classDateServlet/servlet-class /servlet servlet-mapping servlet-nameDateServlet/servlet-name url-pattern/servlet/DateServlet/url-pattern /servlet-mapping -- servlet servlet-nameDDSMenu/servlet-name servlet-classDDSMenu/servlet-class /servlet servlet-mapping servlet-nameDDSMenu/servlet-name url-pattern/DDSMenu/url-pattern /servlet-mapping servlet servlet-nameDDSHome/servlet-name servlet-classDDSHome/servlet-class /servlet servlet-mapping servlet-nameDDSHome/servlet-name url-pattern/DDSHome/url-pattern /servlet-mapping servlet servlet-nameDDSLogin/servlet-name servlet-classDDSLogin/servlet-class /servlet servlet-mapping servlet-nameDDSLogin/servlet-name url-pattern/DDSLogin/url-pattern /servlet-mapping servlet servlet-nameDDSLog/servlet-name servlet-classDDSLog/servlet-class /servlet servlet-mapping servlet-nameDDSLog/servlet-name url-pattern/DDSLog/url-pattern /servlet-mapping /web-app -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- Lajos Moczar Open Source Support, Consulting and Training Cocoon Developer's Handbook (www.amazon.com/exec/obidos/tg/detail/-/0672322579) _ _ / \ / /___\ / / \ / http://www.galatea.com -- powered by AzSSL -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Parse error in application web.xml
Hi, Instead of depending on the invoker servlet, I have added our servlets to Good. 2003-01-17 13:07:51 ContextConfig[/esd] Parse error in application web.xml org.xml.sax.SAXParseException: The content of element type web-app must match (icon?,display-name?,description?,distributable?,context- param*,filter*,fil ter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime- mappin g*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource- ref*,se curity-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb - loca l-ref*). I have validated the web.xml file using IE. No errors are apparent. The You may have viewed the file using IE, not validated it ;) ;) IE would not check against the scheme. The error reported suggests you have elements in the wrong order. It tells you what the right order is. For example, welcome-file-list cannot come before servlet. Reorganize your web.xml file according to the spec, i.e. in the order shown above, and the error will go away. Yoav Shapira Millennium ChemInformatics -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Parse error in application web.xml
That was it. Thanks I placed welcome-file-list element at the bottom and then grouped all of the servlet elements together and underneath it all of the servlet-mapping elements. It finally started up with out an error. Thanks Again. If anybody is interested below is my corrected version. web.xml file: ?xml version=1.0 encoding=ISO-8859-1? !DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application 2.3//EN http://java.sun.com/dtd/web-app_2_3.dtd; web-app servlet servlet-nameDDSMenu/servlet-name servlet-classDDSMenu/servlet-class /servlet servlet servlet-nameDDSHome/servlet-name servlet-classDDSHome/servlet-class /servlet servlet servlet-nameDDSLogin/servlet-name servlet-classDDSLogin/servlet-class /servlet servlet servlet-nameDDSLog/servlet-name servlet-classDDSLog/servlet-class /servlet servlet-mapping servlet-nameDDSMenu/servlet-name url-pattern/DDSMenu/url-pattern /servlet-mapping servlet-mapping servlet-nameDDSHome/servlet-name url-pattern/DDSHome/url-pattern /servlet-mapping servlet-mapping servlet-nameDDSLogin/servlet-name url-pattern/DDSLogin/url-pattern /servlet-mapping servlet-mapping servlet-nameDDSLog/servlet-name url-pattern/DDSLog/url-pattern /servlet-mapping welcome-file-list welcome-fileindex.html/welcome-file welcome-fileindex.htm/welcome-file welcome-fileindex.jsp/welcome-file /welcome-file-list /web-app -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED]] Sent: Friday, January 17, 2003 1:37 PM To: Tomcat Users List Subject: RE: Parse error in application web.xml Hi, Instead of depending on the invoker servlet, I have added our servlets to Good. 2003-01-17 13:07:51 ContextConfig[/esd] Parse error in application web.xml org.xml.sax.SAXParseException: The content of element type web-app must match (icon?,display-name?,description?,distributable?,context- param*,filter*,fil ter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime- mappin g*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource- ref*,se curity-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb - loca l-ref*). I have validated the web.xml file using IE. No errors are apparent. The You may have viewed the file using IE, not validated it ;) ;) IE would not check against the scheme. The error reported suggests you have elements in the wrong order. It tells you what the right order is. For example, welcome-file-list cannot come before servlet. Reorganize your web.xml file according to the spec, i.e. in the order shown above, and the error will go away. Yoav Shapira Millennium ChemInformatics -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Parse error in application web.xml
Hi Jake, Thanks for the reply. I had same exception thrown even with fresh installation of tomcat 4.1.18 without my application included in webapps. Anyway I solved this problem by uninstalling tomcat, removing all classpath settings from environmental variables and installing tomcat again. Now it is working fine, any way this will remain puzzle to me as no one has reported similar bug anywhere else !! - Original Message - From: Jacob Kjome [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Friday, January 03, 2003 11:17 PM Subject: Re: Parse error in application web.xml Sorry, I failed to look at the original question. I just noticed that you were talking about putting stuff in your classpath which, obviously, will have no effect. The trouble you are having is not related to any particular version of Xercesand if you are using j2sdk14.x, you don't need xercesImpl.jar or xmlParserAPIs.jar anyway. You can get rid of them entirely if you want. The problem is your web.xml is not well formed. Check it in an editor such as XMLSpy. First check that it is well formed (all tags are opened and closed and properly nested) and then check to see that it is valid (make sure it obeys the specified DTD). Tomcat will barf in both cases, rightfully so, if the web.xml is bad. BTW, it seems as if you are implying that the problem is with the web.xml in Tomat's conf folder. What makes you assume that? Did you, by chance, put your own app in the webapps folder? If so, try removing that and any other apps that didn't come with Tomcat originally, try starting tomcat, and see if you get the same error. I suspect the problem is likely one of your own apps web.xml's, not a problem with Tomcat. Jake At 03:23 PM 1/3/2003 +0530, you wrote: Hi, I have xercesImpl.jar and xmlParserAPIs.jar files in E:\Tomcat 4.1\common\endorsed directory and followed the instruction by Jan-Michael and I am still getting the exception. I had earlier integrated tomcat 4.1.18 with Apache 2.0.43. and it was working fine and a few days back I started getting these exception when I started tomcat and therefore I did fresh installation of tomcat 4.1.18 and still I am getting the same exception. I am working with windows 2000 regards, Keshav - Original Message - From: Jacob Kjome [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Friday, January 03, 2003 11:49 AM Subject: Re: Parse error in application web.xml Tomcat-3.3.x and above completely ignore the system classpath as far as webapps are concerned. All jar files that you want your webapps to see will have to be in either the WEB-INF/lib of your webapp or in the designated library directories. The only exception to this are the Java runtime classes and jars that you put in JAVA_HOME/jre/lib/endorsed or jre/lib/ext which, essentially, make those jars part of the Java runtime. However, I don't recommend using those techniques for webapps unless you want to spend lots of time trying to debug classloader issues Jake At 08:56 PM 1/2/2003 -0800, you wrote: Hi there, I was reading an unrelated article on this but its possible that just setting your CLASSPATH doesn't really pick up your new xerces parser. Fire up tomcat with this flag -Djava.endorsed.dirs=$CATALINA_HOME/common/endorsed (make sure to put the new JAR files in that directory).. check out http://jakarta.apache.org/tomcat/tomcat-4.1-doc/class-loader- howto.html and scroll down to the section XML Parsers and JDK 1.4 towards the bottom. Hope that helps Jan-Michael - Original Message - From: Keshava Murthy [EMAIL PROTECTED] Date: Thursday, January 2, 2003 8:24 pm Subject: Re: Parse error in application web.xml Hi Jason, I downloaded latest jar files and included them in my classpat I am still getting the same exception regards, keshav - Original Message - From: Bowsher, Jason P [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Thursday, January 02, 2003 6:32 PM Subject: RE: Parse error in application web.xml I had a very similar problem (although not eactly the same). I think, for me, this was a bug in xerces. I upgraded from target=lhttp://www.jpackage.org/rpm.php?id=571 xerces-j2- 2.2.1-1jpp to target=lhttp://www.jpackage.org/rpm.php?id=571 xerces-j2- 2.2.1-2jpp from jpackage.org to fix it. Hope it helps -Original Message- From: Keshava Murthy [mailto:[EMAIL PROTECTED]] Sent: 02 January 2003 12:44 To: [EMAIL PROTECTED] Subject: Parse error in application web.xml Hi, I installed Tomcat 4.1.18 and when I try to start the servlet engine I am getting the following
Re: Parse error in application web.xml
Hi, I have xercesImpl.jar and xmlParserAPIs.jar files in E:\Tomcat 4.1\common\endorsed directory and followed the instruction by Jan-Michael and I am still getting the exception. I had earlier integrated tomcat 4.1.18 with Apache 2.0.43. and it was working fine and a few days back I started getting these exception when I started tomcat and therefore I did fresh installation of tomcat 4.1.18 and still I am getting the same exception. I am working with windows 2000 regards, Keshav - Original Message - From: Jacob Kjome [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Friday, January 03, 2003 11:49 AM Subject: Re: Parse error in application web.xml Tomcat-3.3.x and above completely ignore the system classpath as far as webapps are concerned. All jar files that you want your webapps to see will have to be in either the WEB-INF/lib of your webapp or in the designated library directories. The only exception to this are the Java runtime classes and jars that you put in JAVA_HOME/jre/lib/endorsed or jre/lib/ext which, essentially, make those jars part of the Java runtime. However, I don't recommend using those techniques for webapps unless you want to spend lots of time trying to debug classloader issues Jake At 08:56 PM 1/2/2003 -0800, you wrote: Hi there, I was reading an unrelated article on this but its possible that just setting your CLASSPATH doesn't really pick up your new xerces parser. Fire up tomcat with this flag -Djava.endorsed.dirs=$CATALINA_HOME/common/endorsed (make sure to put the new JAR files in that directory).. check out http://jakarta.apache.org/tomcat/tomcat-4.1-doc/class-loader- howto.html and scroll down to the section XML Parsers and JDK 1.4 towards the bottom. Hope that helps Jan-Michael - Original Message - From: Keshava Murthy [EMAIL PROTECTED] Date: Thursday, January 2, 2003 8:24 pm Subject: Re: Parse error in application web.xml Hi Jason, I downloaded latest jar files and included them in my classpat I am still getting the same exception regards, keshav - Original Message - From: Bowsher, Jason P [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Thursday, January 02, 2003 6:32 PM Subject: RE: Parse error in application web.xml I had a very similar problem (although not eactly the same). I think, for me, this was a bug in xerces. I upgraded from target=lhttp://www.jpackage.org/rpm.php?id=571 xerces-j2- 2.2.1-1jpp to target=lhttp://www.jpackage.org/rpm.php?id=571 xerces-j2- 2.2.1-2jpp from jpackage.org to fix it. Hope it helps -Original Message- From: Keshava Murthy [mailto:[EMAIL PROTECTED]] Sent: 02 January 2003 12:44 To: [EMAIL PROTECTED] Subject: Parse error in application web.xml Hi, I installed Tomcat 4.1.18 and when I try to start the servlet engine I am getting the following error - 003-01-02 17:44:36 ContextConfig 2003-01-02 17:44:36 ContextConfigweb.xml org.xml.sax.SAXParseException: The markup declarations contained or pointed to by the document type declaration must be well-formed. at org.apache.xerces.parsers.AbstractSAXParser.parse (AbstractSAXParser.java:118 9) at org.apache.commons.digester.Digester.parse(Digester.java:1495) at org.apache.catalina.startup.ContextConfig.applicationConfig (ContextConfig.ja va:282) at org.apache.catalina.startup.ContextConfig.start (ContextConfig.java:639) at org.apache.catalina.startup.ContextConfig.lifecycleEvent (ContextConfig.java: 243) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent (LifecycleSuppor t.java:166) at org.apache.catalina.core.StandardContext.start (StandardContext.java:3567) at org.apache.catalina.core.ContainerBase.addChildInternal (ContainerBase.java:8 21) at org.apache.catalina.core.ContainerBase.addChild (ContainerBase.java:807) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:579) at org.apache.catalina.core.StandardHostDeployer.addChild (StandardHostDeployer. java:529) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.beanutils.MethodUtils.invokeMethod (MethodUtils.java:228) at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:260) at org.apache.commons.digester.Digester.endElement(Digester.java:1036) at org.apache.xerces.parsers.AbstractSAXParser.endElement (AbstractSAXParser.jav a:585
Re: Parse error in application web.xml
Sorry, I failed to look at the original question. I just noticed that you were talking about putting stuff in your classpath which, obviously, will have no effect. The trouble you are having is not related to any particular version of Xercesand if you are using j2sdk14.x, you don't need xercesImpl.jar or xmlParserAPIs.jar anyway. You can get rid of them entirely if you want. The problem is your web.xml is not well formed. Check it in an editor such as XMLSpy. First check that it is well formed (all tags are opened and closed and properly nested) and then check to see that it is valid (make sure it obeys the specified DTD). Tomcat will barf in both cases, rightfully so, if the web.xml is bad. BTW, it seems as if you are implying that the problem is with the web.xml in Tomat's conf folder. What makes you assume that? Did you, by chance, put your own app in the webapps folder? If so, try removing that and any other apps that didn't come with Tomcat originally, try starting tomcat, and see if you get the same error. I suspect the problem is likely one of your own apps web.xml's, not a problem with Tomcat. Jake At 03:23 PM 1/3/2003 +0530, you wrote: Hi, I have xercesImpl.jar and xmlParserAPIs.jar files in E:\Tomcat 4.1\common\endorsed directory and followed the instruction by Jan-Michael and I am still getting the exception. I had earlier integrated tomcat 4.1.18 with Apache 2.0.43. and it was working fine and a few days back I started getting these exception when I started tomcat and therefore I did fresh installation of tomcat 4.1.18 and still I am getting the same exception. I am working with windows 2000 regards, Keshav - Original Message - From: Jacob Kjome [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Friday, January 03, 2003 11:49 AM Subject: Re: Parse error in application web.xml Tomcat-3.3.x and above completely ignore the system classpath as far as webapps are concerned. All jar files that you want your webapps to see will have to be in either the WEB-INF/lib of your webapp or in the designated library directories. The only exception to this are the Java runtime classes and jars that you put in JAVA_HOME/jre/lib/endorsed or jre/lib/ext which, essentially, make those jars part of the Java runtime. However, I don't recommend using those techniques for webapps unless you want to spend lots of time trying to debug classloader issues Jake At 08:56 PM 1/2/2003 -0800, you wrote: Hi there, I was reading an unrelated article on this but its possible that just setting your CLASSPATH doesn't really pick up your new xerces parser. Fire up tomcat with this flag -Djava.endorsed.dirs=$CATALINA_HOME/common/endorsed (make sure to put the new JAR files in that directory).. check out http://jakarta.apache.org/tomcat/tomcat-4.1-doc/class-loader- howto.html and scroll down to the section XML Parsers and JDK 1.4 towards the bottom. Hope that helps Jan-Michael - Original Message - From: Keshava Murthy [EMAIL PROTECTED] Date: Thursday, January 2, 2003 8:24 pm Subject: Re: Parse error in application web.xml Hi Jason, I downloaded latest jar files and included them in my classpat I am still getting the same exception regards, keshav - Original Message - From: Bowsher, Jason P [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Thursday, January 02, 2003 6:32 PM Subject: RE: Parse error in application web.xml I had a very similar problem (although not eactly the same). I think, for me, this was a bug in xerces. I upgraded from target=lhttp://www.jpackage.org/rpm.php?id=571 xerces-j2- 2.2.1-1jpp to target=lhttp://www.jpackage.org/rpm.php?id=571 xerces-j2- 2.2.1-2jpp from jpackage.org to fix it. Hope it helps -Original Message- From: Keshava Murthy [mailto:[EMAIL PROTECTED]] Sent: 02 January 2003 12:44 To: [EMAIL PROTECTED] Subject: Parse error in application web.xml Hi, I installed Tomcat 4.1.18 and when I try to start the servlet engine I am getting the following error - 003-01-02 17:44:36 ContextConfig 2003-01-02 17:44:36 ContextConfigweb.xml org.xml.sax.SAXParseException: The markup declarations contained or pointed to by the document type declaration must be well-formed. at org.apache.xerces.parsers.AbstractSAXParser.parse (AbstractSAXParser.java:118 9) at org.apache.commons.digester.Digester.parse(Digester.java:1495) at org.apache.catalina.startup.ContextConfig.applicationConfig (ContextConfig.ja va:282) at org.apache.catalina.startup.ContextConfig.start (ContextConfig.java:639) at org.apache.catalina.startup.ContextConfig.lifecycleEvent (ContextConfig.java: 243) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent
RE: Parse error in application web.xml
I had a very similar problem (although not eactly the same). I think, for me, this was a bug in xerces. I upgraded from http://www.jpackage.org/rpm.php?id=571 xerces-j2-2.2.1-1jpp to http://www.jpackage.org/rpm.php?id=571 xerces-j2-2.2.1-2jpp from jpackage.org to fix it. Hope it helps -Original Message- From: Keshava Murthy [mailto:[EMAIL PROTECTED]] Sent: 02 January 2003 12:44 To: [EMAIL PROTECTED] Subject: Parse error in application web.xml Hi, I installed Tomcat 4.1.18 and when I try to start the servlet engine I am getting the following error - 003-01-02 17:44:36 ContextConfig[/admin]: Occurred at line 1 column 3 2003-01-02 17:44:36 ContextConfig[/admin] Parse error in application web.xml org.xml.sax.SAXParseException: The markup declarations contained or pointed to by the document type declaration must be well-formed. at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:118 9) at org.apache.commons.digester.Digester.parse(Digester.java:1495) at org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.ja va:282) at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:639) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java: 243) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor t.java:166) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3567) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:8 21) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:579) at org.apache.catalina.core.StandardHostDeployer.addChild(StandardHostDeployer. java:529) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:228) at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:260) at org.apache.commons.digester.Digester.endElement(Digester.java:1036) at org.apache.xerces.parsers.AbstractSAXParser.endElement(AbstractSAXParser.jav a:585) at org.apache.xerces.impl.XMLNamespaceBinder.endElement(XMLNamespaceBinder.java :647) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocu mentFragmentScannerImpl.java:1008) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc her.dispatch(XMLDocumentFragmentScannerImpl.java:1469) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocume ntFragmentScannerImpl.java:329) at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:525) at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:581) at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152) at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:117 5) at org.apache.commons.digester.Digester.parse(Digester.java:1514) at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.j ava:335) at org.apache.catalina.core.StandardHost.install(StandardHost.java:803) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:452 ) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:409) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:879) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:368) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor t.java:166) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1196) at org.apache.catalina.core.StandardHost.start(StandardHost.java:738) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347) at org.apache.catalina.core.StandardService.start(StandardService.java:497) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2189) at org.apache.catalina.startup.Catalina.start(Catalina.java:512) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) 2003-01-02 17:44:36 ContextConfig[/admin]: Occurred at line 1 column 3 2003-01-02 17:44:36 ContextConfig[/admin]: Marking this application unavailable due to previous error(s) 2003-01-02 17:44:36 StandardManager[/admin]: Seeding random
Re: Parse error in application web.xml
Hi Jason, I downloaded latest jar files and included them in my classpat I am still getting the same exception regards, keshav - Original Message - From: Bowsher, Jason P [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Thursday, January 02, 2003 6:32 PM Subject: RE: Parse error in application web.xml I had a very similar problem (although not eactly the same). I think, for me, this was a bug in xerces. I upgraded from http://www.jpackage.org/rpm.php?id=571 xerces-j2-2.2.1-1jpp to http://www.jpackage.org/rpm.php?id=571 xerces-j2-2.2.1-2jpp from jpackage.org to fix it. Hope it helps -Original Message- From: Keshava Murthy [mailto:[EMAIL PROTECTED]] Sent: 02 January 2003 12:44 To: [EMAIL PROTECTED] Subject: Parse error in application web.xml Hi, I installed Tomcat 4.1.18 and when I try to start the servlet engine I am getting the following error - 003-01-02 17:44:36 ContextConfig[/admin]: Occurred at line 1 column 3 2003-01-02 17:44:36 ContextConfig[/admin] Parse error in application web.xml org.xml.sax.SAXParseException: The markup declarations contained or pointed to by the document type declaration must be well-formed. at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:118 9) at org.apache.commons.digester.Digester.parse(Digester.java:1495) at org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.ja va:282) at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:639) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java: 243) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor t.java:166) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3567) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:8 21) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:807) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:579) at org.apache.catalina.core.StandardHostDeployer.addChild(StandardHostDeployer. java:529) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:228) at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:260) at org.apache.commons.digester.Digester.endElement(Digester.java:1036) at org.apache.xerces.parsers.AbstractSAXParser.endElement(AbstractSAXParser.jav a:585) at org.apache.xerces.impl.XMLNamespaceBinder.endElement(XMLNamespaceBinder.java :647) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocu mentFragmentScannerImpl.java:1008) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatc her.dispatch(XMLDocumentFragmentScannerImpl.java:1469) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocume ntFragmentScannerImpl.java:329) at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:525) at org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:581) at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152) at org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:117 5) at org.apache.commons.digester.Digester.parse(Digester.java:1514) at org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.j ava:335) at org.apache.catalina.core.StandardHost.install(StandardHost.java:803) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:452 ) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:409) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:879) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:368) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor t.java:166) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1196) at org.apache.catalina.core.StandardHost.start(StandardHost.java:738) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1188) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:347) at org.apache.catalina.core.StandardService.start(StandardService.java:497) at org.apache.catalina.core.StandardServer.start(StandardServer.java:2189) at org.apache.catalina.startup.Catalina.start(Catalina.java:512) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
Re: Parse error in application web.xml
Hi there, I was reading an unrelated article on this but its possible that just setting your CLASSPATH doesn't really pick up your new xerces parser. Fire up tomcat with this flag -Djava.endorsed.dirs=$CATALINA_HOME/common/endorsed (make sure to put the new JAR files in that directory).. check out http://jakarta.apache.org/tomcat/tomcat-4.1-doc/class-loader- howto.html and scroll down to the section XML Parsers and JDK 1.4 towards the bottom. Hope that helps Jan-Michael - Original Message - From: Keshava Murthy [EMAIL PROTECTED] Date: Thursday, January 2, 2003 8:24 pm Subject: Re: Parse error in application web.xml Hi Jason, I downloaded latest jar files and included them in my classpat I am still getting the same exception regards, keshav - Original Message - From: Bowsher, Jason P [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Thursday, January 02, 2003 6:32 PM Subject: RE: Parse error in application web.xml I had a very similar problem (although not eactly the same). I think, for me, this was a bug in xerces. I upgraded from target=lhttp://www.jpackage.org/rpm.php?id=571 xerces-j2- 2.2.1-1jpp to target=lhttp://www.jpackage.org/rpm.php?id=571 xerces-j2- 2.2.1-2jpp from jpackage.org to fix it. Hope it helps -Original Message- From: Keshava Murthy [mailto:[EMAIL PROTECTED]] Sent: 02 January 2003 12:44 To: [EMAIL PROTECTED] Subject: Parse error in application web.xml Hi, I installed Tomcat 4.1.18 and when I try to start the servlet engine I am getting the following error - 003-01-02 17:44:36 ContextConfig 2003-01-02 17:44:36 ContextConfigweb.xml org.xml.sax.SAXParseException: The markup declarations contained or pointed to by the document type declaration must be well-formed. at org.apache.xerces.parsers.AbstractSAXParser.parse (AbstractSAXParser.java:118 9) at org.apache.commons.digester.Digester.parse(Digester.java:1495) at org.apache.catalina.startup.ContextConfig.applicationConfig (ContextConfig.ja va:282) at org.apache.catalina.startup.ContextConfig.start (ContextConfig.java:639) at org.apache.catalina.startup.ContextConfig.lifecycleEvent (ContextConfig.java: 243) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent (LifecycleSuppor t.java:166) at org.apache.catalina.core.StandardContext.start (StandardContext.java:3567) at org.apache.catalina.core.ContainerBase.addChildInternal (ContainerBase.java:8 21) at org.apache.catalina.core.ContainerBase.addChild (ContainerBase.java:807) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:579) at org.apache.catalina.core.StandardHostDeployer.addChild (StandardHostDeployer. java:529) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.beanutils.MethodUtils.invokeMethod (MethodUtils.java:228) at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:260) at org.apache.commons.digester.Digester.endElement(Digester.java:1036) at org.apache.xerces.parsers.AbstractSAXParser.endElement (AbstractSAXParser.jav a:585) at org.apache.xerces.impl.XMLNamespaceBinder.endElement (XMLNamespaceBinder.java :647) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement (XMLDocu mentFragmentScannerImpl.java:1008) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDi spatc her.dispatch(XMLDocumentFragmentScannerImpl.java:1469) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument (XMLDocume ntFragmentScannerImpl.java:329) at org.apache.xerces.parsers.DTDConfiguration.parse (DTDConfiguration.java:525) at org.apache.xerces.parsers.DTDConfiguration.parse (DTDConfiguration.java:581) at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152) at org.apache.xerces.parsers.AbstractSAXParser.parse (AbstractSAXParser.java:117 5) at org.apache.commons.digester.Digester.parse(Digester.java:1514) at org.apache.catalina.core.StandardHostDeployer.install (StandardHostDeployer.j ava:335) at org.apache.catalina.core.StandardHost.install(StandardHost.java:803) at org.apache.catalina.startup.HostConfig.deployDescriptors (HostConfig.java:452 ) at org.apache.catalina.startup.HostConfig.deployApps (HostConfig.java:409) at org.apache.catalina.startup.HostConfig.start (HostConfig.java:879) at org.apache.catalina.startup.HostConfig.lifecycleEvent (HostConfig.java:368) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent (LifecycleSuppor t.java:166) at org.apache.catalina.core.ContainerBase.start
Re: Parse error in application web.xml
Tomcat-3.3.x and above completely ignore the system classpath as far as webapps are concerned. All jar files that you want your webapps to see will have to be in either the WEB-INF/lib of your webapp or in the designated library directories. The only exception to this are the Java runtime classes and jars that you put in JAVA_HOME/jre/lib/endorsed or jre/lib/ext which, essentially, make those jars part of the Java runtime. However, I don't recommend using those techniques for webapps unless you want to spend lots of time trying to debug classloader issues Jake At 08:56 PM 1/2/2003 -0800, you wrote: Hi there, I was reading an unrelated article on this but its possible that just setting your CLASSPATH doesn't really pick up your new xerces parser. Fire up tomcat with this flag -Djava.endorsed.dirs=$CATALINA_HOME/common/endorsed (make sure to put the new JAR files in that directory).. check out http://jakarta.apache.org/tomcat/tomcat-4.1-doc/class-loader- howto.html and scroll down to the section XML Parsers and JDK 1.4 towards the bottom. Hope that helps Jan-Michael - Original Message - From: Keshava Murthy [EMAIL PROTECTED] Date: Thursday, January 2, 2003 8:24 pm Subject: Re: Parse error in application web.xml Hi Jason, I downloaded latest jar files and included them in my classpat I am still getting the same exception regards, keshav - Original Message - From: Bowsher, Jason P [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Thursday, January 02, 2003 6:32 PM Subject: RE: Parse error in application web.xml I had a very similar problem (although not eactly the same). I think, for me, this was a bug in xerces. I upgraded from target=lhttp://www.jpackage.org/rpm.php?id=571 xerces-j2- 2.2.1-1jpp to target=lhttp://www.jpackage.org/rpm.php?id=571 xerces-j2- 2.2.1-2jpp from jpackage.org to fix it. Hope it helps -Original Message- From: Keshava Murthy [mailto:[EMAIL PROTECTED]] Sent: 02 January 2003 12:44 To: [EMAIL PROTECTED] Subject: Parse error in application web.xml Hi, I installed Tomcat 4.1.18 and when I try to start the servlet engine I am getting the following error - 003-01-02 17:44:36 ContextConfig 2003-01-02 17:44:36 ContextConfigweb.xml org.xml.sax.SAXParseException: The markup declarations contained or pointed to by the document type declaration must be well-formed. at org.apache.xerces.parsers.AbstractSAXParser.parse (AbstractSAXParser.java:118 9) at org.apache.commons.digester.Digester.parse(Digester.java:1495) at org.apache.catalina.startup.ContextConfig.applicationConfig (ContextConfig.ja va:282) at org.apache.catalina.startup.ContextConfig.start (ContextConfig.java:639) at org.apache.catalina.startup.ContextConfig.lifecycleEvent (ContextConfig.java: 243) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent (LifecycleSuppor t.java:166) at org.apache.catalina.core.StandardContext.start (StandardContext.java:3567) at org.apache.catalina.core.ContainerBase.addChildInternal (ContainerBase.java:8 21) at org.apache.catalina.core.ContainerBase.addChild (ContainerBase.java:807) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:579) at org.apache.catalina.core.StandardHostDeployer.addChild (StandardHostDeployer. java:529) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.beanutils.MethodUtils.invokeMethod (MethodUtils.java:228) at org.apache.commons.digester.SetNextRule.end(SetNextRule.java:260) at org.apache.commons.digester.Digester.endElement(Digester.java:1036) at org.apache.xerces.parsers.AbstractSAXParser.endElement (AbstractSAXParser.jav a:585) at org.apache.xerces.impl.XMLNamespaceBinder.endElement (XMLNamespaceBinder.java :647) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement (XMLDocu mentFragmentScannerImpl.java:1008) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDi spatc her.dispatch(XMLDocumentFragmentScannerImpl.java:1469) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument (XMLDocume ntFragmentScannerImpl.java:329) at org.apache.xerces.parsers.DTDConfiguration.parse (DTDConfiguration.java:525) at org.apache.xerces.parsers.DTDConfiguration.parse (DTDConfiguration.java:581) at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152) at org.apache.xerces.parsers.AbstractSAXParser.parse (AbstractSAXParser.java:117 5) at org.apache.commons.digester.Digester.parse(Digester.java:1514) at org.apache.catalina.core.StandardHostDeployer.install
