Are you outputting error messages using h:messages?
Yes I do. I fail to see the connection with the behaviour of the commandButton.
Normally the reason for a action not being executed is that there have been failures in one of the JSF phases and you've forgotten to output JSF errors using h:messages. Of course you don't get this using s:button as it doesn't submit the form.
Sorry for the long breaks in reply. Some of us in Africa do not have very reliable internet connections.
Well, if that is the case then i'd expect the h:messages to output whatever message there is and still allow me to go on with the commandButton. Is there no way i can get around this?
You'll need to read a good JSF book/tutorial to find out all about the JSF lifecycle.
Hi Pete and Damatrix,
I 've the same problem of Damatric... where I must looking for?
I solved in my code,
I think that the problem is in the
tabPanel switchType="ajax", if I use the switchType="client" it make do!
I suppose that the problem be the ajax switch
I hope help you Damatrix.
I face the same problem as Damatrix, and with the <h:messages > tag, I could see the problem. When the commandButton is pressed, a message "Conversion Error" appears.
As I using a simple <h:inputText> tag with a String content, I´m not understanding what is happenig.
Could anyone help me?
With the previous replies to my post, i thought that i new version of RichFaces will solve my problem but after downloading and using RichFaces 3.1.2.GA, my commandButtons and commandLinks on tabPanels still do not work.
Please, someone help. I'm stuck.
Post this on the RF forum, I don't think it has anything to do with Seam.
Other person have the same problem...
They are different, but not the same.
1. Using h:commandLink (but not the h:commandButton) inside the h:form after Ajax re-rendering has a limitation due the specific of h:commandLink architecture. I t
old many times about it and mentioned at least twice on the richfaces-demo:
2. Most common problems with "action is not invoked":
a) validation/conversion problems
b) form inside form (does not allowed by JSF)
c) Using ajaxSingle="true" together with immediate="true"
3. Action method is invoked at the fifth phase (if immediate flag is not set). So, if fifth phase is bypassed , it needs to figure our why it is bypassed instead of why the action is not called. The phase tracker is useful to detect where the normal lifecycle is interrupted. Ready-to-use phase tracker is here: http://www.jsftutorials.net/faces-config/phaseTracker.html
Thanks for the last post, SergeySmirnov. The problem was a form in another form as you can see from my very first post. You saved me.