1 Reply Latest reply on Oct 24, 2011 6:15 PM by Jason Porter

    Seam Faces @ViewScoped in GET request: replacement for JSF 2 @ViewScoped c:forEach or component binding bean loss?

    Karsten Wutzke Expert

      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:

      @ViewScoped Managed bean loads many times during postback

      Use of JSTL/core tags screws up ViewScoped Bean

      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.