The Seam 3 Faces module contains the CDI @ViewScoped annotation. Does this annotation resolve the JSF 2 issues described here (http://balusc.blogspot.com/2010/06/benefits-and-pitfalls-of-viewscoped.html)?
I really need rich:tabPanel rich:tab's from iterative data along with a view-scoped bean, but using c:forEach or the component binding both cause the view-scoped bean to be destroyed after any AJAX requests. Note the page is called with a simple GET param in the browser, e.g.
The issue I'm experiencing has been described here:
Note that setting javax.faces.PARTIAL_STATE_SAVING to false didn't work for me yet (exceptions thrown).
Does the Seam 3 Faces @ViewScoped circumvent the above JSF 2 issue, which won't be fixed anytime soon?
Feel free to make some
wild guesses here, any discussion coming up would probably lead to something useful.
The @ViewScoped in Seam Faces is completely different, so it very well may fix those issues, only one way to find out though :)
I haven't seen the bean being loaded many times when I have used it. Not sure about JSTL though as I haven't used them for a while.