This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
The rendered attribute is also determined during apply request values phase of the subsequent request (the form submit). You need to make sure that the getter behind the rendered attribute returns the same value as it did in the initial request (for display). Change the bean's logic, or use h:inputHidden with binding, or Tomahawk's t:saveState, or -more ridiculous-, set the bean in the session scope instead of request scope. [ December 18, 2008: Message edited by: Bauke Scholtz ]
Joined: Jul 09, 2008
thanks for the reply agin,
I don't think its the problem with scope,
If it is so, the logic should not work at all, I mean the button should not show up or should show up all the time.
But the display works fine, the buttons functionality is not working-- the button is not calling the action it is supposed to if I have this particular expression in the rendered tag.
That works fine if change the expression or remove it completely.
I hope you got what I am trying to explain here.
Joined: Oct 08, 2006
Read on about the JSF lifecycle and then reread my answer.