Re: submitOnEvent callback

Bug is resolved - please try with the nightly snapshot. In any case, rendered should have worked before. regards, Martin On Feb 2, 2008 2:29 AM, Dave [EMAIL PROTECTED] wrote: Hi Martin, I have filed a bug in MyFaces jira. http://issues.apache.org/jira/browse/TOMAHAWK-1187 I also suggest

Re: submitOnEvent callback

the bean method return a string that is a javascript function name. Mario Ivankovits [EMAIL PROTECTED] wrote: Hi! callback=#{bean.callbackFunction} The callback should point to a javascript function name instead of a bean method. callback is meant to be executed on the client. This javascript

Re: submitOnEvent callback

Hi Dave, don`t know why the method is not called, maybe Mario knows it. It`s not that nice, but you may also write: callback=mySpecialUserCallback .. function mySpecialUserCallback(event, srcComponentId, clickComponentId) { return #{bean.submitOnChange}; } This should work without any

Re: submitOnEvent callback

I have prepared a fix and will commit it, if someone (Dave?) provides me with an issue-number ;) regards, Martin On 2/1/08, Martin Marinschek [EMAIL PROTECTED] wrote: Hi guys, the clue is that restoreState/saveState was implemented wrongly in submitOnEvent - another reason to get the

Re: submitOnEvent callback

Hi guys, the clue is that restoreState/saveState was implemented wrongly in submitOnEvent - another reason to get the component-generator up and running. This is the erronous code - it uses the getter to access the component-attributes (and will therefore store the return-value of the method as

Re: submitOnEvent callback

Hi Martin, I have filed a bug in MyFaces jira. http://issues.apache.org/jira/browse/TOMAHAWK-1187 I also suggest adding a onsubmit=javascript code that can return true/false. Thanks. dave Martin Marinschek [EMAIL PROTECTED] wrote: I have prepared a fix and will commit it,

submitOnEvent callback

for s:submitOnEvent, in my case, whether to submit depends on a bean variable. So I need a rendered property. h:selectOneMenu s:submitOnEvent for=aButton event=change rendered=#{bean.submitOnChange} / /h:selectOneMenu h:commandButton id=aButton .../ But the

Re: submitOnEvent callback

callback=#{bean.callbackFunction} The bean method is not called. Dave [EMAIL PROTECTED] wrote:for s:submitOnEvent, in my case, whether to submit depends on a bean variable. So I need a rendered property. h:selectOneMenu s:submitOnEvent for=aButton event=change

Re: submitOnEvent callback

Hi! callback=#{bean.callbackFunction} The callback should point to a javascript function name instead of a bean method. callback is meant to be executed on the client. This javascript method then should allow you to return true/false, on false the click should not happen. Ciao, Mario