[ http://issues.apache.org/jira/browse/TOMAHAWK-838?page=all ]
Ondrej Svetlik resolved TOMAHAWK-838.
-------------------------------------
Resolution: Invalid
Sorry for that... I must have done something wrong, it calls the
getters/setters always the same way.
> commandSortHeader calls getters/setters in a different order for
> request/session scoped beans
> ---------------------------------------------------------------------------------------------
>
> Key: TOMAHAWK-838
> URL: http://issues.apache.org/jira/browse/TOMAHAWK-838
> Project: MyFaces Tomahawk
> Issue Type: Bug
> Components: Extended Datatable
> Affects Versions: 1.1.3, 1.1.5-SNAPSHOT
> Environment: x86_64, fedora core 6
> java version "1.5.0_06"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
> Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_06-b05, mixed mode)
> tomcat 5.5.20
> Reporter: Ondrej Svetlik
>
> I have a dataTable with sortColumn and sortAscending set to fields of a
> managed bean. The same bean provides the data for the table.
> When the bean is session scoped, first the setters for sortColumn and
> sortAscending are called with the right values, then the getter of the data.
> When it is request scoped, first the getter of data is called, then the
> setters for sortColumn and sortAscending.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
