You can reproduce the issues we're seeing by deploying the
tomahawk-examples-1.1.9-bin.zip war file and making a few adjustments to it
to bring it up to date with JSF 1.2.  Once the following modification are
made to the examples web app, you will notice that it works fine under
tomcat 6.0.24 but no longer resolves simple EL expression in 6.0.26

1)      Deploy the 'myfaces-example-simple-1.1.9.war' file from
tomahawk-examples-1.1.9-bin.zip
(http://www.apache.org/dyn/closer.cgi/myfaces/binaries/tomahawk-examples-1.1
.9-bin.zip) to tomcat 6.0.26

2)      Navigate to myfaces-example-simple-1.1.9\WEB-INF\lib

3)      Remove the following JAR files:
        myfaces-api-1.1.7.jar
        myfaces-impl-1.1.7.jar
        tomahawk-1.1.9.jar

4)      Add the following jar files
        myfaces-api-1.2.8.jar
        myfaces-impl-1.2.8.jar
        tomahawk12-1.1.9.jar
        commons-discovery-0.4.jar

5)      Start the tomcat server and navigate to
http://host:8080/myfaces-example-simple-1.1.9/sample1.jsf.  You will notice
that the many EL expressions are not resolved properly.

6)      Do the same for 6.0.24 and the screen will render as expected.

Thanks,

Erick

-----Original Message-----
From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] 
Sent: Friday, March 12, 2010 4:00 PM
To: Tomcat Users List
Subject: Re: Issues with Tomcat 6.0.26

2010/3/12 Sai Pullabhotla <sai.pullabho...@jmethods.com>:
> I forgot to mention the version numbers in my previous mail. Here they
are:
>
> Richfaces 3.3.1
> MyFaces 1.2.4
> Tomahawk 1.1.6
>

I have just downloaded trinidad-1.2.13-example.zip and
its trinidad-demo-1.2.13.war works for me in 6.0.26.

Cannot find usable tomahawk or richfaces examples:

tomahawk-examples-1.1.8-bin.zip is for MyFaces 1.1 / Servlet 2.4,
irrelevant here
richfaces-examples-3.3.2.SR1.zip (photoalbum) requires JBoss


In short, parsing in Tomcat 6.0.26 was made more strict to the version
of specification that your web application, your tag library and the
tag that you are calling are using.

The change was to address bug 48668. Most likely this commit is what
affected you:
http://svn.apache.org/viewvc?rev=920916&view=rev

Please make sure that
1) Your web.xml adheres to the Servlet 2.5 specification
I.e., starts with

<web-app xmlns="http://java.sun.com/xml/ns/javaee";
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd";
         version="2.5">

2) The TLD file for the tag library that you are using adheres to the
JSP 2.1 specification.

>  <taglib xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
>  http://java.sun.com/xml/ns/javaee/web-jsptaglibrary_2_1.xsd";
>    xmlns="http://java.sun.com/xml/ns/javaee";
>  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; version="2.1">

Yes, that is JSP 2.1

Note, that <taglib> element in web.xml can be used to specify
different location for the TLD file. If the file is not specified in
web.xml, make sure that <uri> element value in your TLD file matches
URI that you used for your tags. That is, to make sure that you are
looking on the actual TLD file that was used.

Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4940 (20100312) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com


 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4940 (20100312) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to