More flexible state saving

[glassfishrobot]

In JSF the user can choose to save state on the server or the client via the javax.faces.STATE_SAVING_METHOD context parameter. Because this is a global setting that applies to all views in the application, it's not really flexible.

I would like to propose making this more flexible. Ideally the user would have three options for state: none (see #1055), client and server and would be able to set this globally, per URL pattern, or per view.

Setting the state saving method on a view would override any setting done per URL pattern, and setting state saving for a URL pattern overrides the global setting.

[glassfishrobot]

Reported by @arjantijms

[glassfishrobot]

@edburns said:
Although this would be very useful, we have to leave this as Fix Version unknown because I haven't figured out yet how to fit it into JSF 2.2.

[glassfishrobot]

@edburns said:
Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.

[glassfishrobot]

@manfredriem said:
Closing this issue as "Incomplete" as the scope is too large. Note that the EG wants work in the area of state saving, but I have told them the scope of the issue to tackle things needs to be smaller.

[glassfishrobot]

Marked as incomplete on Thursday, September 10th 2015, 6:30:07 am

[glassfishrobot]

This issue was imported from java.net JIRA JAVASERVERFACES_SPEC_PUBLIC-1056