You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Guy Bashan (JIRA)" <de...@myfaces.apache.org> on 2006/01/11 17:04:20 UTC
[jira] Commented: (MYFACES-1019) JSF initial state
[ http://issues.apache.org/jira/browse/MYFACES-1019?page=comments#action_12362461 ]
Guy Bashan commented on MYFACES-1019:
-------------------------------------
This issue is not a bug, it is Improvement. I hope you read it ... The first part deals with the problem, the second part deals with suggested improvement.
> JSF initial state
> -----------------
>
> Key: MYFACES-1019
> URL: http://issues.apache.org/jira/browse/MYFACES-1019
> Project: MyFaces
> Type: Improvement
> Components: Implementation
> Versions: 1.1.1
> Environment: Linux, WindowXP, JDeveloper
> Reporter: Guy Bashan
>
> I am having this problem for a long time and lost any hope of getting a decent answer in any forum:
> It seems like JSF does not give any solution to initial state problem.
> A simple example:
> I want to show a simple table that is being updated according to several filters.
> The table should be shown with initial data according to filters selections.
> The actions that I am doing are:
> 1) To show initially the table, on the backing bean constructor I am loading the table data.
> 2) On any "valueChange" of every filter I want to load the new data of the table also, so I load the data again.
> This causes the data of the table to be loaded twice: once in the constructor and second in the value change listener method.
> This problem happens in many variations many times in JSF. Is there a way of initializing data properly ?
> For example, I would expect that in addition to the constructor there will be 2 additional methods:
> 1) init() - Will be called when screen first loads.
> 2) reinit() - Will be called when screen is reloaded.
> Am I missing here something ? Or there is a solid agreed way of solving the initial state term in JSF.
> By the way, I have to initialize data dynamically and not using managed properties.
--
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