Bug 38653 - "parameterMap.locked" message does not exist
Summary: "parameterMap.locked" message does not exist
Status: RESOLVED FIXED
Alias: None
Product: Tomcat 5
Classification: Unclassified
Component: Servlet & JSP API (show other bugs)
Version: 5.5.14
Hardware: All All
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-15 12:23 UTC by Nicolas Ternisien
Modified: 2006-02-16 08:37 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Ternisien 2006-02-15 12:23:06 UTC
The Map returned from HttpServletRequest is in fact a specifical class, called
ParameterMap.

This map does not allow to modify any key or value of it, and in the case the
user tries to, it launches a IllegalStateException. 

The problem is that the key string used does not exist.

So to fix this bug you need to add the parameterMap.locked key/value in
properties files of the Servlet API.

Begin of the trace :
javax.servlet.ServletException: Cannot find message associated with key
'parameterMap.locked'

There is also a little-little bug in the Javadoc of ParameterMap class :

/**
 * Extended implementation of <strong>HashMap</strong> that includes a
 * <code>locked</code> property.  This class can be used to safely expose
 * Catalina internal parameter map objects to user classes without having
 * to clone them in order to avoid modifications.  When first created, a
 * <code>ParmaeterMap</code> instance is not locked.
 *
 * @author Craig R. McClanahan
 * @version $Revision: 302726 $ $Date: 2004-02-27 09:59:07 -0500 (Fri, 27 Feb
2004) $
 */

public final class ParameterMap extends HashMap {

The "<code>ParmaeterMap</code>" string should be replaced by
"<code>ParameterMap</code>"

Bye !

PS: This bug also occurs in Tomcat 3 and 4.