-
Bug
-
Resolution: Done
-
Major
-
3.0.0.GA
-
None
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 "#
" (see https://jira.jboss.org/jira/browse/JBIDE-4048).
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 https://jira.jboss.org/jira/browse/JBIDE-3336)
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="#
">
<h:column><h:outputText value="#
</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="#
">
<h:column><h:outputText value="#
"/></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).
- is related to
-
JBIDE-4514 Improve performance of Seam Validator when a Java file is modified
- Closed
- relates to
-
JBIDE-4048 dataTable var can't be resolved
- Closed