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

Bug 200181

Summary: JSP Editor wrongly states that a scripting-varibale "cannot be resolved"
Product: [WebTools] WTP Source Editing Reporter: Oliver Henning <oliver.henning>
Component: jst.jspAssignee: Nitin Dahyabhai <thatnitind>
Status: RESOLVED DUPLICATE QA Contact: Nitin Dahyabhai <thatnitind>
Severity: normal    
Priority: P3 CC: Yannick.Savanier
Version: 2.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Screenshot of JSP-Editor none

Description Oliver Henning CLA 2007-08-16 08:10:35 EDT
Created attachment 76213 [details]
Screenshot of JSP-Editor

Build ID: I20070621-1340

Steps To Reproduce:
1. import the JSP-File (see below) into an Eclipse-Projekt
2. include some struts.jar (e.g. Version 1.2.9) in your Build-Path
3. open the JSP-File with the JSP-Editor

The JSP-File is as follows:
-----------------------------------------------------------------
<%@taglib uri="http://struts.apache.org/tags-nested" prefix="nested" %>
<nested:define name="monoBean" id="monoBean" type="ch.aloba.SomeBean" />

<nested:iterate property="rowList">
	<nested:iterate property="columnList" indexId="id" id="xxx">
		bla bla bla
	</nested:iterate>
	<%Object o1=monoBean;%>
</nested:iterate>
<%Object o2=monoBean;%>
-----------------------------------------------------------------


More information:
In this special case i use some JSP-Tags from Struts (from the nested-Tag-Library). In Line 2 there is a definition of a Scripting-Variable called "monoBean".

In Line 8 the access is ok for the JSP-Editor. In Line 10 the Editor states that monoBean cannot be resolved. But in Tomcat,JBoss and WebSphere this JSP compiles well and works as expected.
Comment 1 Yannick Savanier CLA 2008-07-01 08:06:49 EDT
This is a clone of bug 239002.
Actually your problem is only due to the presence of the indexId attribute into your nested iterate tag wich totally break the jsp parser loose and therefore all validation or debbuging.
I suggest to mark the bug as duplicate of bug 239002 wich indentify the problem more clearly.
Comment 2 Nitin Dahyabhai CLA 2008-07-08 08:39:43 EDT

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