[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-4512) "var cannot be resolved" does not recognize single value

"var cannot be resolved" does not recognize single value -------------------------------------------------------- Key: JBIDE-4512 URL: https://jira.jboss.org/jira/browse/JBIDE-4512 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.0.0.GA Environment: JBossTools-ALL-win32-3.0.1.GA-R200905070146-H18, Seam 2.1.1.GA Reporter: Julien Kronegg Attachments: MyBean.java Jboss Tools does not recognize correctly the "var" property in list iterators (e.g. rich:dataTable, h:dataTable) if the "value" property is a single value (but works if the "value" property is a List. This problem occurs for XHTML pages generated by seam-gen where the value is "#{myEntityHome.instance.singleValue}" (see <a href=https://jira.jboss.org/jira/browse/JBIDE-4048>JBIDE-4048</a>). Effects: 1. add a lot of warnings "variableName cannot be resolved" that should be there 2. makes "Seam Validator" task to be very slow when there is a lot of pages (because the Seam Validator task is run on each XHTML file with at least one unresolved EL, see <a href=https://jira.jboss.org/jira/browse/JBIDE-3336>JBIDE-3336</a>) Expected: As the rich:dataTable displays one row when the "value" property is a single value and not a list, Jboss Tools is expected to recognize list AND single value. How to reproduce: EXECUTE: Create seam project. EXECUTE: Create MyBean component (see attached java file) EXECUTE: Open home.xhtml EXECUTE: Add: <h:dataTable var="myVar" value="#{myBean.values}"> <h:column><h:outputText value="#{myVar.myProperty}"/></h:column> </h:dataTable> <h:dataTable var="myVar" value="#{myBean.singleValue}"> <h:column><h:outputText value="#{myVar.myProperty}"/></h:column> </h:dataTable> <h:dataTable var="myVar" value="#{myBean.singleValueAsList}"> <h:column><h:outputText value="#{myVar.myProperty}"/></h:column> </h:dataTable> ASSERT: no warning "myVar cannot be resolved" appear Workaround: Use a "value" property as List and not as single value (maybe wrapping the single value to a List should do the trick).