Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.2
    • Component/s: None
    • Labels:
      None

      Description

      As documented and implemented here, a Stateless JSF operation mode would be incredibly useful for high-load applications and architectures:

      http://industrieit.com/blog/2011/11/stateless-jsf-high-performance-zero-per-request-memory-overhead/#comment-4

      This has previously been suggested by Jacob: http://weblogs.java.net/blog/jhook/archive/2006/01/experiment_goin.html

      This would help JSF ditch the stigma of "slow and memory hog," and help keep up with current tech trends (statless architectures.)

        Issue Links

          Activity

          Hide
          kito75 added a comment -

          I'd like to see a console warning, not just a FacesMessage. A FacesMessage may not be displayed in production, and doesn't show up in the logs.

          Show
          kito75 added a comment - I'd like to see a console warning, not just a FacesMessage. A FacesMessage may not be displayed in production, and doesn't show up in the logs.
          Hide
          exabrial added a comment -

          Hey I know this issue is closed, but on a closely related feature request, could this be extended slightly to specify the state saving method on a per-view basis? So there'd be 'none','server','client'? I think I saw this in JIRA somewhere but I can't find the feature request.

          Show
          exabrial added a comment - Hey I know this issue is closed, but on a closely related feature request, could this be extended slightly to specify the state saving method on a per-view basis? So there'd be 'none','server','client'? I think I saw this in JIRA somewhere but I can't find the feature request.
          Hide
          kithouna added a comment -

          I think I saw this in JIRA somewhere but I can't find the feature request.

          JAVASERVERFACES_SPEC_PUBLIC-1056

          It would be great if this too would have been included, but the work for JSF 2.2 has to stop at some point, otherwise there'll never be a release.

          I really hope that issue will be one of the first things addressed for 2.3

          Show
          kithouna added a comment - I think I saw this in JIRA somewhere but I can't find the feature request. JAVASERVERFACES_SPEC_PUBLIC-1056 It would be great if this too would have been included, but the work for JSF 2.2 has to stop at some point, otherwise there'll never be a release. I really hope that issue will be one of the first things addressed for 2.3
          Hide
          Ertio lew added a comment -

          Would viewscope work in stateless mode ?

          It would be good if viewscope works in stateless mode or otherwise there is some appropriate substitute for replacing viewscope.

          Show
          Ertio lew added a comment - Would viewscope work in stateless mode ? It would be good if viewscope works in stateless mode or otherwise there is some appropriate substitute for replacing viewscope.
          Hide
          arjan tijms added a comment -

          Would viewscope work in stateless mode?

          No, it explicitly doesn't work. If you try it JSF will throw a specific exception to warn you about this.

          It would be good if viewscope works in stateless mode or otherwise there is some appropriate substitute for replacing viewscope.

          There should be something, but personally I think this would only make sense when it's possible to make a distinction between "state" and "cache". In a stateless mode it would defeat the purpose to use a bean that keeps state, but it might very well be used for cache. In this context I then define "state" as unique data and "cache" as data that can be restored somehow.

          Show
          arjan tijms added a comment - Would viewscope work in stateless mode? No, it explicitly doesn't work. If you try it JSF will throw a specific exception to warn you about this. It would be good if viewscope works in stateless mode or otherwise there is some appropriate substitute for replacing viewscope. There should be something, but personally I think this would only make sense when it's possible to make a distinction between "state" and "cache". In a stateless mode it would defeat the purpose to use a bean that keeps state, but it might very well be used for cache. In this context I then define "state" as unique data and "cache" as data that can be restored somehow.

            People

            • Assignee:
              Ed Burns
              Reporter:
              lincolnbaxter
            • Votes:
              47 Vote for this issue
              Watchers:
              39 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 4 hours, 3 minutes
                4h 3m