Re: actionListener not invoked

2006-08-02 Thread Mike Kienenberger
On 7/26/06, mjovanov [EMAIL PROTECTED] wrote: Now the actionListener in so longer firing. Any suggestions? I tried using t:savestate but could not on the columns bean as it is a DataModel (not Serializable)... I have never tried it, but I think you can use t:saveState on

Re: actionListener not invoked

2006-07-26 Thread mjovanov
not on the columns bean as it is a DataModel (not Serializable)... -- View this message in context: http://www.nabble.com/actionListener-not-invoked-tf1317007.html#a5505589 Sent from the MyFaces - Users forum at Nabble.com.

Re: actionListener not invoked

2006-03-22 Thread Mike Kienenberger
The confusion is probably caused by the fact that a UICommand component needs to have a rendered attribute that is page-scoped rather than request-scoped. The rendered attribute value needs to remain constant from the first request's RenderResponse phase until the next request's InvokeApplication

Re: actionListener not invoked

2006-03-22 Thread Dean Hiller
huh, very interesting. thanks for the explanation. I am slowly getting there. from the last posted answer and this one. dean Mike Kienenberger wrote: The confusion is probably caused by the fact that a UICommand component needs to have a rendered attribute that is page-scoped rather than

actionListener not invoked

2006-03-21 Thread Murat Hazer
A simple page has two linkst:commandLink id=link1 actionListener=#{backer.edit} value=Edit rendered=#{back.enabled} / t:commandLink id=link2 actionListener=#{backer.enableEdit} value=Enable Edit /When the enable edit link is cliked 'enabled' property of the backing bean is changed to true so that

Re: actionListener not invoked

2006-03-21 Thread Mike Kienenberger
My guess is that you are not persisting the value of #{back.enabled} between requests. In order for a UICommand to work, it must remain enabled (rendered=true) from the first request renderResponse phase to the next request's invokeApplication phase. Maybe all you need to do is use t:saveState

Re: actionListener not invoked

2006-03-21 Thread Dennis Byrne
You may want to look on the wiki for this. Find the FAQ section and scroll all the way to the bottom. Dennis Byrne -Original Message- From: Murat Hazer [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 21, 2006 07:10 AM To: users@myfaces.apache.org Subject: actionListener not invoked

Re: actionListener not invoked

2006-03-21 Thread Murat Hazer
Thanks for all answers, i solved the problem with t:savestate. (also al80 on the IRC channel helped me to solve the problem.)On 3/21/06, Dennis Byrne [EMAIL PROTECTED] wrote: (You may want to look on the wiki for this.Find the FAQ section and scroll all the way to the bottom. Dennis

Re: actionListener not invoked

2006-03-21 Thread Dean Hiller
I am confused by the response. if back.enabled was false, he would not be able to click the commanLink, would he? It sounds like he was saying backer.edit was not working. Maybe my question is a stupid question from a newb(me), but could you explain that response more so I can understand.

Re: actionListener not invoked

2006-03-21 Thread Murat Hazer
the backer bean to the session scope, but i think it is not very clever solution), the Edit link's (id=link1) actionListener isn't invoked(actionListener=#{ backer.edit}). (but you can see the code to invoke the method in the source of the generated html page, this was confused my mind).As i told