could you show us some code, it's hard to come up with a workaround if we don't know what you're trying to do. Although, what is ugly on a single form?
Using only one form requires coding a little bit more and be more careful when makes changes in complex and big form. There is another workaround using PrimeFaces, the jsf bug is resolved on js level but I'd like to see that RF also comes with some solution out of the box.
To reproduce the bug you need one form with r:jsFunction rendering a second form. The viewState in the second form is lost.
1 of 1 people found this helpful
The original issue that mechtatel is referencing:
The fix for this is in RichFaces 5, but there are other ViewState problems with JSF 2.2 that we are trying to work through, namely:
mechtatel could you confirm that this works for you with JSF 2.1 (and RichFaces 5) but is broken when switching to JSF 2.2? We expect to have full JSF 2.2 compatibility with the upcoming RichFaces 5.0.0.Alpha3.
Another closest bug is [RF-10963] a4j:commandButton doesn't update the hidden javax.faces.ViewState from render form - JBoss Issue Tracker. Probably they are several bugs related to this main issue.
At this moment I don't have chance to test in JSF 2.1, but I'm happy to know that all this bugs related to the viewState and ajax render will be fixed in RF 5.0.0.Alpha3 with the full JSF 2.2 compatibility.
Congratulations for the RF 5.0.0.Alpha2 release. I see a lot of potential with the Polyglot Widgets! I'd like to see soon more components.