Re: commandbutton does not call the backend bean

2010-09-29 Thread Xiaobo Yang
Thanks. I've resolved the problem. It is related to the selectOneRadio
component I used. - Xiaobo

On 28 September 2010 16:43, Christian Kaltepoth christ...@kaltepoth.de wrote:
 Seems like the validation failed for some reason. Did you add a
 h:messages to the page? You could also try to skip the model update
 (and valdiation) by setting the immediate attribute of the button to
 true.

 Christian


 2010/9/28, Xiaobo Yang xiaobo.y...@gmail.com:
 Hi all,

 I'm using MyFaces 1.1.5 and Tomahawk 1.1.6 in an application and got a
 problem with a button. When I clicked the button, it did not call the
 backend bean but stayed in the same page. I noticed the lines below in
 the log file.

 org.apache.myfaces.lifecycle.LifecycleImpl - exiting from
 lifecycle.execute in PROCESS_VALIDATIONS(3) because getRenderResponse
 is true from one of the after listeners
 org.apache.myfaces.lifecycle.LifecycleImpl - entering
 RENDER_RESPONSE(6) in org.apache.myfaces.lifecycle.LifecycleImpl

 Could anybody explain what are the possible reasons to cause
 PROCESS_VALIDATIONS to stop?

 Many thanks,
 Xiaobo



 --
 Christian Kaltepoth
 Blog: http://chkal.blogspot.com/
 Twitter: http://twitter.com/chkal



commandbutton does not call the backend bean

2010-09-28 Thread Xiaobo Yang
Hi all,

I'm using MyFaces 1.1.5 and Tomahawk 1.1.6 in an application and got a
problem with a button. When I clicked the button, it did not call the
backend bean but stayed in the same page. I noticed the lines below in
the log file.

org.apache.myfaces.lifecycle.LifecycleImpl - exiting from
lifecycle.execute in PROCESS_VALIDATIONS(3) because getRenderResponse
is true from one of the after listeners
org.apache.myfaces.lifecycle.LifecycleImpl - entering
RENDER_RESPONSE(6) in org.apache.myfaces.lifecycle.LifecycleImpl

Could anybody explain what are the possible reasons to cause
PROCESS_VALIDATIONS to stop?

Many thanks,
Xiaobo