Henkel-
web.xml will need to map xsd to some known mime-type e.g.
<mime-mapping>
<extension>xsd</extension>
<mime-type>text/xml</mime-type>
</mime-mapping>
Also I would look at
ValidateVisitor.visit(Validator.java:423)
for any expressions which you are currently not handling
(Velocity/Freemarker comes to mind)
Martin--
----- Original Message -----
Wrom: NHGSWZIDREXCAXZOWCONEUQZAAFXISHJEXXIMQZUIVO
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Wednesday, November 14, 2007 8:26 AM
Subject: JasperException in Tomcat 5.0 and above but not in 4.1
> Hello everybody.
>
> We are still using Tomcat 4.1 and JDK 1.4.2 for a web application.
> I'm trying to modernize this now and switch to Tomcat 5.x or 6 and
> JRE/JDK 1.6 (Java 6).
>
> While I was successful with Tomcat 4.1 and JDK 1.6, whenever I try to
> use Tomcat 5.x or 6, I receive error messages like below, when pushing a
> button (which will call a new page) in most of our "wizard" dialogs.
>
> I changed web.xml to refer to web-app version 2.4 (.../web-app_2_4.xsd).
>
> The error messages look like this:
>
> org.apache.jasper.JasperException:
> /wizard/manualAssignment/assignOrder.jsp(76,0) The name attribute of the
> jsp:param standard action does not accept any expressions
> at
>
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.
java:39)
>
> at
>
org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:409
)
>
> at
>
org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:238
)
>
> at
>
org.apache.jasper.compiler.Validator$ValidateVisitor.throwErrorIfExpression(
Validator.java:1157)
>
> at
>
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:42
3)
>
> at org.apache.jasper.compiler.Node$ParamAction.accept(Node.java:927) at
> org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2163) at
> org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2213) at
>
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:44
6)
>
> at org.apache.jasper.compiler.Node$IncludeAction.accept(Node.java:1002)
> at org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2163) at
> org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2213) at
>
org.apache.jasper.compiler.Validator$ValidateVisitor.visit(Validator.java:71
6)
>
> at org.apache.jasper.compiler.Node$CustomTag.accept(Node.java:1441) at
> org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2163) at
> org.apache.jasper.compiler.Node$Visitor.visitBody(Node.java:2213) at
> org.apache.jasper.compiler.Node$Visitor.visit(Node.java:2219) at
> org.apache.jasper.compiler.Node$Root.accept(Node.java:456) at
> org.apache.jasper.compiler.Node$Nodes.visit(Node.java:2163) at
> org.apache.jasper.compiler.Validator.validate(Validator.java:1475) at
> org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:214) at
> org.apache.jasper.compiler.Compiler.compile(Compiler.java:495)
> .....
>
> When I look into that file (assignOrder.jsp) there is - in line 77 -
> after an <jsp:include ...> in line 76 a
> <jsp:param name="<%= [some variable] %>" value="<%= [some expression ]
%>"/>
>
> Isn't this possible in Tomcat 5 and above?
> Why?
>
> I found some spec for jsp:param where it was explicity stated,
> that "value" can be an <%= %> expression, but "name" cannot ... for JSP
> 1.2 which was used by Tomcat 4.1.
>
> So is Tomcat 5.x and above just more strict in checking this?
> Is there a way to tell Tomcat 5.x/6 to be "compatible" to Tomcat 4.1 (be
> less strict)?
>
> Thanks for any help!
>
> With kind regards,
> Harald Henkel
> GS automation GmbH
>
>
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
