1 2 Previous Next 21 Replies Latest reply on Jan 9, 2007 1:07 PM by c_eric_ray Go to original post
      • 15. Re: @Out frustration
        texan
        texan Sep 7, 2006 5:06 PM (in response to texan)

        I'm using "client" state saving. Funny you should ask - I tried switching to "server" to see what would happen, and all of my "commandButton" and "commandLink" controls stopped working (s:link still worked). I don't know why they quit working, but I quickly reset it back to "client".

          • Actions
        • 16. Re: @Out frustration
          cptnkirk Sep 7, 2006 5:09 PM (in response to texan)

          My guess is the client vs server state saving problem is due to a bug in ealier versions of MyFaces that JBoss may still ship with.

            • Actions
          • 17. Re: @Out frustration
            cptnkirk Sep 7, 2006 5:13 PM (in response to texan)

            ...or maybe that was an earlier version of facelets (or both). Try upgrading those if you need server side state saving.

              • Actions
            • 18. Re: @Out frustration
              texan
              texan Sep 7, 2006 5:18 PM (in response to texan)

              I'm using (as far as I know) the latest released versions of facelets, my faces, and tomahawk. However, I could try the CVS versions to see if they fixed the problem.

              The jury's still out (in my head anyway) on server vs. client. The usual tradeoff - server means that I don't have to send as much junk out to the browser, client means that I'm storing more on the server and might run out of memory with lots of users...

              I'm still in a pilot stage of my app right now, with a handful of users. They're on an old Servlet/JSP code base, whiie I upgrade the technology to Seam/JSF and add features. Scares me a little to be learning all this at once (never used JSF), but it's a good way to insure that I learn fast.

                • Actions
              • 19. Re: @Out frustration
                newlukai Oct 4, 2006 10:11 AM (in response to texan)

                I have this client vs. server error, too. I have to use client state saving, since if I use server state saving the login button doesn't work. Could you solve the problem?

                  • Actions
                • 20. Re: @Out frustration
                  c_eric_ray Jan 9, 2007 1:04 PM (in response to texan)

                   

                  "CptnKirk" wrote:
                  @Out's scope defaults to the scope of the enclosing controller, in this case the SLSB. SLSB have a stateless scope. I think that Seam may actually promote the outjection of context variables of stateless components to event scope for you (but I'm not positive).

                  Event scope is like JSP request scope and page scope is like JSP page scope. My guess is this example didn't work for you because you used </redirect> navigation in your JSF action. If so, your view came in two requests. The first outjected the Bean, then left scope. Then you made the next request to view the page and saw everthing with their original values.

                  I hope this clears up the scoping question.


                  I'm experiencing this very problem(although, I'm using SFSB). The only way I can get my application to work with outjection is to set everything to SESSION scope. I do use page navigation and as soon as I change scope to anythign less than SESSION, nothing gets outjected.

                  In another post Gavin says SESSION scope is bad and it is a memory leak. Now I'm really worried. How do you solve this problem?

                    • Actions
                  • 21. Re: @Out frustration
                    c_eric_ray Jan 9, 2007 1:07 PM (in response to texan)

                    here's the qout from Gavin...

                    But the reality is that a SESSION scoped persistence context is always a bad thing (it is a memory leak, to begin with), and you should never do that.


                    I guess I don't understand.

                      • Actions
                    1 2 Previous Next