1 2 Previous Next 17 Replies Latest reply on Jun 4, 2009 9:47 AM by nbelaevski Go to original post
      • 15. Re: java.util.NoSuchElementException
        dobreden1 Jun 4, 2009 9:01 AM (in response to dobreden1)

        When you say 'no problem' what do you mean - That the request scope bean will keep state? Shouldn't we use binding with RichFaces?

          • Actions
        • 16. Re: java.util.NoSuchElementException
          ilya_shaikovsky
          ilya_shaikovsky Jun 4, 2009 9:07 AM (in response to dobreden1)

          1) RichFaces adds any restrictions. Just JSF itself works in this way with session scoped bindings. Such usage not recommended in JSF itself. Not sure about specification 1.2 but 2.0 specification already has this highlighted. You could google "session scoped bindings in JSF" and see how manyu problems could appear even without RF ;) Also Nick already explained some JSF related problems above.

          2) Nick meant that the info you need could be stored without bindings usage.

            • Actions
          • 17. Re: java.util.NoSuchElementException
            nbelaevski
            nbelaevski Jun 4, 2009 9:47 AM (in response to dobreden1)

             

            "dobreden1" wrote:
            I have beans in session scope because they hold data that I don't want to initialise on each request, e.g. a list of values displayed in a table or state about a component.

            No problem, store components state in session either as data.

              • Actions
            1 2 Previous Next