A reader on StackOverflow said that downgrading to Richfaces 3.3 fixed this problem for him. I really can't do that, though it suggests that it is definately a bug. Can someone verify that it is a known bug please? If so, has it been fixed in the latest stable release, 4.2.2.Final?
At this point, I would prefer to have a workaround. Do I need to bind the tabPanel and manipulate it in a backing bean?
Well, I upgraded to 4.2.2.Final and it still doesn't work.
This is the question on StackOverflow.
If this is not supported, I wish one of the Richfaces developers would just tell me and save me the trouble of trying.
1 of 1 people found this helpful
onclick is to early and if you return true, how should the ajax request been send?
Okay, I must say, I only have experience with richfaces 3.3.x
But I think an option could be switching the tab in your backing bean:
Use the FacesContext current instance, find the tabPanel and call the switchTo function (if there is such a thing) and add the tabPanel to the rerender queue.
(this is what I would try in richfaces 3.3.3)
I added a second f:setPropertyActionListener to set the TabPanel's activeItem to EditTab. Then I added oncomplete="location.reload(true);" to refresh everything and redraw with the correct active tab.
It works, but I'd still like to hear a better approach.
Thanks for responding Christian.
Does simple rerending of only the tabpanel / your output containers not work or why do you have to reload the whole page?
The render= didn't seem to work. Any ideas?
Hi, I think you should use oncomplete, and investigate why swith part js not work, and even more you can write a js function to swith tab.