Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 4532 invoked from network); 29 Jul 2010 02:46:44 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 29 Jul 2010 02:46:44 -0000 Received: (qmail 67450 invoked by uid 500); 29 Jul 2010 02:46:44 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 66902 invoked by uid 500); 29 Jul 2010 02:46:42 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 66888 invoked by uid 99); 29 Jul 2010 02:46:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Jul 2010 02:46:41 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Jul 2010 02:46:38 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o6T2kGjj024787 for ; Thu, 29 Jul 2010 02:46:16 GMT Message-ID: <24069546.60261280371576276.JavaMail.jira@thor> Date: Wed, 28 Jul 2010 22:46:16 -0400 (EDT) From: "Guang Zhe Wang (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Updated: (GERONIMO-5478) JSP 2.2 new configuration element under works incorrectly on tomcat-assembly server. In-Reply-To: <3919136.60051280370915936.JavaMail.jira@thor> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/GERONIMO-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guang Zhe Wang updated GERONIMO-5478: ------------------------------------- Patch Info: [Patch Available] Description: is said to specify the default response contentType if the page directive does not include a contentType attribute in the JSP 2.2 spec documentation. So does it mean if the page directive have included a contentType attribute, the configuration in will take no effect? In jetty-assembly, it does like this. But in tomcat-assembly, it sends out an exception: org.apache.jasper.JasperException: /defaultCtype/page1.jsp(17,1) Page directive: illegal to have multiple occurrences of contentType with different values (old: text/xml, new: text/html) org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40) org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407) org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:236) org.apache.jasper.compiler.Validator$DirectiveVisitor.visit(Validator.java:133) org.apache.jasper.compiler.Node$PageDirective.accept(Node.java:590) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2376) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2428) org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2434) org.apache.jasper.compiler.Node$Root.accept(Node.java:475) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2376) org.apache.jasper.compiler.Validator.validateDirectives(Validator.java:1733) org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:195) org.apache.jasper.compiler.Compiler.compile(Compiler.java:360) org.apache.jasper.compiler.Compiler.compile(Compiler.java:340) org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:594) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:315) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265) javax.servlet.http.HttpServlet.service(HttpServlet.java:668) I patched the test case I use and uploaded it. You can apply it on trunk. And then build and deploy it on tomcat-assembly to see the result. was: is said to specify the default response contentType if the page directive does not include a contentType attribute in the JSP 2.2 spec documentation. So does it mean if the page directive have included a contentType attribute, the configuration in will take no effect? In jetty-assembly, it does like this. But in tomcat-assembly, it sends out an exception: org.apache.jasper.JasperException: /defaultCtype/page1.jsp(17,1) Page directive: illegal to have multiple occurrences of contentType with different values (old: text/xml, new: text/html) org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40) org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407) org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:236) org.apache.jasper.compiler.Validator$DirectiveVisitor.visit(Validator.java:133) org.apache.jasper.compiler.Node$PageDirective.accept(Node.java:590) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2376) org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2428) org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2434) org.apache.jasper.compiler.Node$Root.accept(Node.java:475) org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2376) org.apache.jasper.compiler.Validator.validateDirectives(Validator.java:1733) org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:195) org.apache.jasper.compiler.Compiler.compile(Compiler.java:360) org.apache.jasper.compiler.Compiler.compile(Compiler.java:340) org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:594) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:315) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265) javax.servlet.http.HttpServlet.service(HttpServlet.java:668) The test case > JSP 2.2 new configuration element under works incorrectly on tomcat-assembly server. > --------------------------------------------------------------------------------------------------------------------------------- > > Key: GERONIMO-5478 > URL: https://issues.apache.org/jira/browse/GERONIMO-5478 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Tomcat > Affects Versions: 3.0 > Reporter: Guang Zhe Wang > Fix For: 3.0 > > Attachments: jsp2.2-testsuite.patch > > > is said to specify the default response contentType if the page directive does not include a contentType attribute in the JSP 2.2 spec documentation. So does it mean if the page directive have included a contentType attribute, the configuration in will take no effect? In jetty-assembly, it does like this. But in tomcat-assembly, it sends out an exception: > org.apache.jasper.JasperException: /defaultCtype/page1.jsp(17,1) Page directive: illegal to have multiple occurrences of contentType with different values (old: text/xml, new: text/html) > org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40) > org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407) > org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:236) > org.apache.jasper.compiler.Validator$DirectiveVisitor.visit(Validator.java:133) > org.apache.jasper.compiler.Node$PageDirective.accept(Node.java:590) > org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2376) > org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2428) > org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2434) > org.apache.jasper.compiler.Node$Root.accept(Node.java:475) > org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2376) > org.apache.jasper.compiler.Validator.validateDirectives(Validator.java:1733) > org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:195) > org.apache.jasper.compiler.Compiler.compile(Compiler.java:360) > org.apache.jasper.compiler.Compiler.compile(Compiler.java:340) > org.apache.jasper.compiler.Compiler.compile(Compiler.java:327) > org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:594) > org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:315) > org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320) > org.apache.jasper.servlet.JspServlet.service(JspServlet.java:265) > javax.servlet.http.HttpServlet.service(HttpServlet.java:668) > I patched the test case I use and uploaded it. You can apply it on trunk. And then build and deploy it on tomcat-assembly to see the result. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.