You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tiles.apache.org by "Antonio Petrelli (JIRA)" <ji...@apache.org> on 2010/08/27 21:09:57 UTC
[jira] Updated: (TILES-514) Let tiles-jsp.tld implement JSP 2.0
[ https://issues.apache.org/jira/browse/TILES-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Petrelli updated TILES-514:
-----------------------------------
Summary: Let tiles-jsp.tld implement JSP 2.0 (was: Update JSP version requirement on the main site. It claims JSP 2.0 is required, but in reality JSP 2.1 is required.)
Description:
Currently, tiles-jsp.tld uses XML Schema of the JSP 2.1 version. It should use the 2.0 version, as specified in the website.
--------Original request--------
I developed an application using tiles2.2.2 (including the core,api,servlet, and jsp components) and it ran fine on my Jetty development container. But, when I deployed to an OC4J 10.1.3.5 container (my production container), It failed with the following error:
Invalid or unsupported tld version: 2.1
The web site (http://tiles.apache.org/framework/getting_started.html) states that JSP 2.0 is required, but digging in the source code, I see that the tld does indeed require JSP 2.1 in versions greater than 2.0.7.
Unless backwards compatibility is a project goal, just updating the site with correct dependency is probably enough. Meanwhile, I'll go back and use the older version until our production site upgrades containers.
was:
I developed an application using tiles2.2.2 (including the core,api,servlet, and jsp components) and it ran fine on my Jetty development container. But, when I deployed to an OC4J 10.1.3.5 container (my production container), It failed with the following error:
Invalid or unsupported tld version: 2.1
The web site (http://tiles.apache.org/framework/getting_started.html) states that JSP 2.0 is required, but digging in the source code, I see that the tld does indeed require JSP 2.1 in versions greater than 2.0.7.
Unless backwards compatibility is a project goal, just updating the site with correct dependency is probably enough. Meanwhile, I'll go back and use the older version until our production site upgrades containers.
I changed the issue description, because the TLD should use 2.0 version of JSP.
> Let tiles-jsp.tld implement JSP 2.0
> -----------------------------------
>
> Key: TILES-514
> URL: https://issues.apache.org/jira/browse/TILES-514
> Project: Tiles
> Issue Type: Task
> Components: site, tiles-jsp (jsp support)
> Affects Versions: 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2.0, 2.2.1, 2.2.2
> Environment: OC4J 10.1.3.5
> Reporter: Gus
> Priority: Minor
>
> Currently, tiles-jsp.tld uses XML Schema of the JSP 2.1 version. It should use the 2.0 version, as specified in the website.
> --------Original request--------
> I developed an application using tiles2.2.2 (including the core,api,servlet, and jsp components) and it ran fine on my Jetty development container. But, when I deployed to an OC4J 10.1.3.5 container (my production container), It failed with the following error:
> Invalid or unsupported tld version: 2.1
> The web site (http://tiles.apache.org/framework/getting_started.html) states that JSP 2.0 is required, but digging in the source code, I see that the tld does indeed require JSP 2.1 in versions greater than 2.0.7.
> Unless backwards compatibility is a project goal, just updating the site with correct dependency is probably enough. Meanwhile, I'll go back and use the older version until our production site upgrades containers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.