[
https://jira.jboss.org/jira/browse/RF-7510?page=com.atlassian.jira.plugin...
]
Wayne Bagguley reopened RF-7510:
--------------------------------
Please read my bug report carefully.
I said that the problem occurred when I tied 'sortOrder' to a bean field. In your
test you just hard-coded the sortOrder.
In my code I have to tie 'sortOrder' to an object in a map:
sortOrder="action.columns['columnNameHere'].sortOrder"
Thus, if 'rendered' for this column is set to
"action.columns['columnNameHere'] ne null" then this will cause an
exception because the sortOrder will still get evaluated, giving a NPE.
sortOrder being evaluated even though rendered=false for rich:column
--------------------------------------------------------------------
Key: RF-7510
URL:
https://jira.jboss.org/jira/browse/RF-7510
Project: RichFaces
Issue Type: Bug
Components: component-tables
Affects Versions: 3.3.1
Environment: Win XP, JBoss 4.2.3, Seam 2.1.2
Reporter: Wayne Bagguley
Assignee: Tsikhon Kuprevich
Priority: Minor
Fix For: 3.3.2.CR1
I have some <rich:column> tags inside a rich:dataTable and some have the
'rendered' attribute tied to a bean field. If this bean field is false, indicating
that there is no data for this column, the 'sortOrder' attribute on the
<rich:column> tag is still evaluated and thus raises an exception because it returns
a null value because that column doesn't exist in the data.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira