Tomcat 5.0.14 + JSTL: SAX Exception
I simply put this line in a page: %@ taglib prefix=c uri=http://java.sun.com/jstl/core; % And I get this exception when trying to load it: org.apache.jasper.JasperException: Validation error messages from TagLibraryValidator for c null: org.xml.sax.SAXParseException: The content of elements must consist of well-formed character data or markup. org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:94) org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:404) org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:112) org.apache.jasper.compiler.Validator.validateXmlView(Validator.java:1575) org.apache.jasper.compiler.Validator.validate(Validator.java:1521) org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:253) org.apache.jasper.compiler.Compiler.compile(Compiler.java:459) org.apache.jasper.compiler.Compiler.compile(Compiler.java:442) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:552) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:291) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:301) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:248) javax.servlet.http.HttpServlet.service(HttpServlet.java:856) What am I doing wrong? Is it possible to use JSTL with Tomcat 5.0.14? Thank you, --Leo __ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SAX Exception
I get these exceptions SEVERE: Parse Error at line 175 column 12: Element type listener must be declared. org.xml.sax.SAXParseException: Element type listener must be declared. SEVERE: Parse Error at line 176 column 25: Element type listener-class must be declared. org.xml.sax.SAXParseException: Element type listener-class must be declared. The corresponding lines of web.xml area: listener listener-classcom.keymind.core.users.UserSessionListener/listener-class /listener The funny thing is... the listener class works just fine. No errors at runtime. That exception is thrown when I start up Tomcat. I am running Tomcat 4.1.24 any suggestions or ideas? Thanks in advance, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: SAX Exception
Howdy, Is your web.xml valid according to the Servlet Specification v2.3 DTD? Yoav Shapira Millennium ChemInformatics -Original Message- From: Turansky, Mark [mailto:[EMAIL PROTECTED] Sent: Monday, July 14, 2003 11:16 AM To: [EMAIL PROTECTED] Subject: SAX Exception I get these exceptions SEVERE: Parse Error at line 175 column 12: Element type listener must be declared. org.xml.sax.SAXParseException: Element type listener must be declared. SEVERE: Parse Error at line 176 column 25: Element type listener-class must be declared. org.xml.sax.SAXParseException: Element type listener-class must be declared. The corresponding lines of web.xml area: listener listener-classcom.keymind.core.users.UserSessionListener/listener- class /listener The funny thing is... the listener class works just fine. No errors at runtime. That exception is thrown when I start up Tomcat. I am running Tomcat 4.1.24 any suggestions or ideas? Thanks in advance, Mark - 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: SAX Exception
aha!! Ok, I looked at the xml dtd declaration at the top... the error was that my web.xml said http://java.sun.com/j2ee/dtds/web-app_2_2.dtd; when it should be 2.3 ! I compared my web.xml with the web.xml file from the example apps and saw the discrepancy. That makes all the difference in the world. mark -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Monday, July 14, 2003 11:24 AM To: Tomcat Users List Subject: RE: SAX Exception Howdy, Is your web.xml valid according to the Servlet Specification v2.3 DTD? Yoav Shapira Millennium ChemInformatics -Original Message- From: Turansky, Mark [mailto:[EMAIL PROTECTED] Sent: Monday, July 14, 2003 11:16 AM To: [EMAIL PROTECTED] Subject: SAX Exception I get these exceptions SEVERE: Parse Error at line 175 column 12: Element type listener must be declared. org.xml.sax.SAXParseException: Element type listener must be declared. SEVERE: Parse Error at line 176 column 25: Element type listener-class must be declared. org.xml.sax.SAXParseException: Element type listener-class must be declared. The corresponding lines of web.xml area: listener listener-classcom.keymind.core.users.UserSessionListener/listener- class /listener The funny thing is... the listener class works just fine. No errors at runtime. That exception is thrown when I start up Tomcat. I am running Tomcat 4.1.24 any suggestions or ideas? Thanks in advance, Mark - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Start up Sax exception init param
Thanks for answering But, do you mean the error is from the cocoon web.xml file or the tomcat one? As I have only changed the cocoon jar, i guess it's from the cocoon one. Here is line 181 !-- This parameter allows you to startup Cocoon2 immediately after startup of your servlet engine. -- load-on-startup1/load-on-startup /servlet Nobody answered my question on the cocoon user mailing list, maybe it was badly fomulated. - Original Message - From: Craig R. McClanahan [EMAIL PROTECTED] To: Tomcat User Mail List [EMAIL PROTECTED]; cib [EMAIL PROTECTED] Sent: Thursday, August 23, 2001 5:48 PM Subject: Re: Start up Sax exception init param On Thu, 23 Aug 2001, cib wrote: Date: Thu, 23 Aug 2001 08:54:24 +0200 From: cib [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED], cib [EMAIL PROTECTED] To: Tomcat User Mail List [EMAIL PROTECTED] Subject: Start up Sax exception init param Hi, I've upgraded to Cocoon2.0b1 from beta1. But since I changed the war old war file to the new one ( I've erased the work directory before, idem for the log files), I get an exception at Tomcat's start. No one answered my question on cocoon mailing list, so I try it here. The exception is: PARSE error at line 181 column -1 org.xml.sax.SAXParseException: org.apache.crimson.parser/V-036 web-app init-param This sounds like there might be a problem with your web.xml file at line 181. In particular, if you have the elements in an order different than what the DTD requires, you will *always* get XML validation errors. Craig McClanahan
Re: Start up Sax exception init param
On Sun, 26 Aug 2001, cib wrote: Date: Sun, 26 Aug 2001 23:17:29 +0200 From: cib [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED], cib [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Start up Sax exception init param Thanks for answering But, do you mean the error is from the cocoon web.xml file or the tomcat one? Since you didn't give us the entire error traceback, it's impossible to tell -- but if it were the Tomcat one, it would cause problems for *all* web apps, not just this one. As I have only changed the cocoon jar, i guess it's from the cocoon one. Here is line 181 !-- This parameter allows you to startup Cocoon2 immediately after startup of your servlet engine. -- load-on-startup1/load-on-startup /servlet Please cut-and-paste the *entire* servlet element -- if things are out of order, we can't tell from just this. Craig Nobody answered my question on the cocoon user mailing list, maybe it was badly fomulated. - Original Message - From: Craig R. McClanahan [EMAIL PROTECTED] To: Tomcat User Mail List [EMAIL PROTECTED]; cib [EMAIL PROTECTED] Sent: Thursday, August 23, 2001 5:48 PM Subject: Re: Start up Sax exception init param On Thu, 23 Aug 2001, cib wrote: Date: Thu, 23 Aug 2001 08:54:24 +0200 From: cib [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED], cib [EMAIL PROTECTED] To: Tomcat User Mail List [EMAIL PROTECTED] Subject: Start up Sax exception init param Hi, I've upgraded to Cocoon2.0b1 from beta1. But since I changed the war old war file to the new one ( I've erased the work directory before, idem for the log files), I get an exception at Tomcat's start. No one answered my question on cocoon mailing list, so I try it here. The exception is: PARSE error at line 181 column -1 org.xml.sax.SAXParseException: org.apache.crimson.parser/V-036 web-app init-param This sounds like there might be a problem with your web.xml file at line 181. In particular, if you have the elements in an order different than what the DTD requires, you will *always* get XML validation errors. Craig McClanahan
RE: Start up Sax exception init param
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]] On Thu, 23 Aug 2001, cib wrote: Date: Thu, 23 Aug 2001 08:54:24 +0200 From: cib [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED], cib [EMAIL PROTECTED] To: Tomcat User Mail List [EMAIL PROTECTED] Subject: Start up Sax exception init param Hi, I've upgraded to Cocoon2.0b1 from beta1. But since I changed the war old war file to the new one ( I've erased the work directory before, idem for the log files), I get an exception at Tomcat's start. No one answered my question on cocoon mailing list, so I try it here. The exception is: PARSE error at line 181 column -1 org.xml.sax.SAXParseException: org.apache.crimson.parser/V-036 web-app init-param This sounds like there might be a problem with your web.xml file at line 181. In particular, if you have the elements in an order different than what the DTD requires, you will *always* get XML validation errors. Craig McClanahan If you take a peek inside crimson.jar, you'll find a properties file (org\apache\crimson\parser\resources\Messages_en.properties) with the full English messages: So 'org.apache.crimson.parser/V-036 web-app init-param' actually means 'Element web-app does not allow init-param here.' There must be a way to get the crimson parser to use these human readable forms for errors... Luc Vanlerberghe
Start up Sax exception init param
Hi, I've upgraded to Cocoon2.0b1 from beta1. But since I changed the war old war file to the new one ( I've erased the work directory before, idem for the log files), I get an exception at Tomcat's start. No one answered my question on cocoon mailing list, so I try it here. The exception is: PARSE error at line 181 column -1 org.xml.sax.SAXParseException: org.apache.crimson.parser/V-036 web-app init-param Everything seems to work fine, but I had to put my mm.mysql.jar file inside the Cocoon web-inf/lib, because it couldn't find my mysql drivers. I haven't changed anything in the Tomcat server.xml nor web.xml files. So what has it got to do with the war file I created? Here is my today mystery. Here is my complete start screeen: G:\Tomcat\binG:\Tomcat\bin\startup.bat Using CLASSPATH: g:\Tomcat\bin\bootstrap.jar;G:\jdk1.3.1\lib\tools.jar; Starting service Tomcat-Standalone Apache Tomcat/4.0-b5 PARSE error at line 181 column -1 org.xml.sax.SAXParseException: org.apache.crimson.parser/V-036 web-app init-param Starting service Tomcat-Apache Apache Tomcat/4.0-b5 Thanks for a clue. Cib France, Bordeaux, xml and gay pride.
Re: Start up Sax exception init param
On Thu, 23 Aug 2001, cib wrote: Date: Thu, 23 Aug 2001 08:54:24 +0200 From: cib [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED], cib [EMAIL PROTECTED] To: Tomcat User Mail List [EMAIL PROTECTED] Subject: Start up Sax exception init param Hi, I've upgraded to Cocoon2.0b1 from beta1. But since I changed the war old war file to the new one ( I've erased the work directory before, idem for the log files), I get an exception at Tomcat's start. No one answered my question on cocoon mailing list, so I try it here. The exception is: PARSE error at line 181 column -1 org.xml.sax.SAXParseException: org.apache.crimson.parser/V-036 web-app init-param This sounds like there might be a problem with your web.xml file at line 181. In particular, if you have the elements in an order different than what the DTD requires, you will *always* get XML validation errors. Craig McClanahan
