[#UP-1241] JSTL 1.1 support in portlet

uPortal

JSTL 1.1 support in portlet

Created: 22/Sep/05 01:07 PM Updated: 29/Aug/07 05:31 PM

Component/s:

Portlet Container

Affects Version/s:

2.3.5, 2.4, 2.4.1, 2.4.2, 2.5.0 M1, 2.6.0 M1, 2.5.1 RC1, 2.5.0 RC1, 2.5.0 RC3, 2.5.0 RC2, 2.5.0 GA, 2.5.1 RC2, 2.5.2 RC1, 2.4.4, 2.4.3, 2.5.1 RC3, 2.5.1 GA, 2.4.3.1, 2.5.3 RC1, 2.5.2 GA, 2.5.3 RC2, 2.5.3 RC3, 2.5.3 GA, 2.6.0 RC1, 2.6.0 RC2, 2.5.3.1

Fix Version/s:

2.6.0 GA

Original Estimate:	Unknown	Remaining Estimate:	Unknown	Time Spent:	Unknown
Environment:	Linux,mysql 4, uPortal 2.3.5+,ant 1.6.5,sdk1.4 ,Tomcat 5.0.28

Description

« Hide

In order to use jstl 1.1 web.xml must be like(Servlet 2.4 JSP 2.0 support):

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
version="2.4">
.................
</web-app>

after portlet deployment I have web.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
................
</web-app>
------------------
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
version="2.4">
otherwise the jstl 1.1 won't work

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Christopher J. Holdorph [21/Feb/07 12:34 AM]

I can validate that this issue still affects uPortal 2.5.3 and most likely every version of uPortal before 2.5.3 that supports portlets.

[ Permlink | « Hide ]

Andrew Wills [03/Jul/07 07:06 PM]

I re-implemented the deployPortletApp target using Cernunnos (http://code.google.com/p/cernunnos/). The previous version ran into issues like the one described here because it hand-crafted a new web.xml when it deployed a portlet application, pulling only a few data elements from the existing one. The new implementation using the web.xml found in the portlet application, only adding a few nodes required by pluto if they're not already there.