112527 – JSP validator treats accessing map values by a constant string key as "EL syntax error"

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 112527 - JSP validator treats accessing map values by a constant string key as "EL syntax error"

Summary: JSP validator treats accessing map values by a constant string key as "EL syn...

Status:	RESOLVED DUPLICATE of bug 136795

Alias:	None

Product:	WTP Source Editing
Classification:	WebTools
Component:	jst.jsp (show other bugs)
Version:	0.7.1
Hardware:	All All

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Ian Tewksbury
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-10-13 14:11 EDT by Fyodor Golos
Modified:	2009-06-15 10:56 EDT (History)
CC List:	3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Fyodor Golos

2005-10-13 14:11:40 EDT

Consider the following JSP file test.jsp:

<%@ page language="java" %>
<html>
<body>
param["yin"] = "${param["yin"]}"
</body>
</html>

Deployed to Tomcat 5.5 and pulled up in a browser as /test.jsp?yin=yang gives:

<html>
<body>
param["yin"] = "yang"
</body>
</html>

However, JSP validator displays the following message with severity of zero in
the Problems view:

"EL Syntax Error"

Looks like JSP validator does not like the quotes used to specify map's key.

Comment 1 David Williams

2005-11-12 01:00:05 EST

Phil, judging from the abstract, this appears your area of expertise?

Comment 2 Vladimir Nicolici

2006-02-27 08:05:57 EST

I also get this warning for code that looks like this, and that code works fine:

<option value="${reason['element_id']}">
	${reason['description_text']}
</option>

Comment 3 David Williams

2006-03-28 03:24:06 EST

Mass transfer from pa to dw. Needs more triage.

Comment 4 Taro App

2008-12-12 02:57:13 EST

Looks like this has been fixed in WTP 3.0.3. (See bug#136795)

Comment 5 Ian Tewksbury

2009-06-15 10:56:14 EDT


*** This bug has been marked as a duplicate of bug 136795 ***