Re: commandButton action not executed

2008-04-08 Thread Scott Belnap
Martin, I was able to solve the issue using t:saveState. Thanks for the help On Tue, 2008-04-08 at 19:32 -0600, Martin Marinschek wrote: > Hi Scott, > > you need the rendered property to remain constant over requests. > > What you could do: > > - use t:saveState > - use a conversation scope >

Re: commandButton action not executed

2008-04-08 Thread Martin Marinschek
Hi Scott, you need the rendered property to remain constant over requests. What you could do: - use t:saveState - use a conversation scope regards, Martin On Wed, Apr 2, 2008 at 7:15 PM, Scott Belnap <[EMAIL PROTECTED]> wrote: > todoListBean is request scoped not session scoped. Is there any

Re: commandButton action not executed

2008-04-02 Thread Scott Belnap
todoListBean is request scoped not session scoped. Is there anyway to use a request scoped bean in this case? Thanks. On Wed, 2008-04-02 at 11:10 -0600, Andrew Robinson wrote: > Is todoListBean session scoped? If your todoList is not available > during decode, the rendered will fail and non-rend

Re: commandButton action not executed

2008-04-02 Thread Andrew Robinson
Is todoListBean session scoped? If your todoList is not available during decode, the rendered will fail and non-rendered components are not decoded. On Wed, Apr 2, 2008 at 10:54 AM, Scott Belnap <[EMAIL PROTECTED]> wrote: > I have a page that has the following commandButton. > >rendered="#{tod

commandButton action not executed

2008-04-02 Thread Scott Belnap
I have a page that has the following commandButton. When I click on the button it doesn't execute the action it just refreshes the page. But if I remove the rendered property so the commanButton tag looks like: jsf will execute the action #{todoListBean.update}. Does anyone know why when I