| Re: [faces-dev] Remove deprecated methods from jakarta.faces.application.StateManager |
Hi,On Wed, Sep 1, 2021 at 5:47 PM David Matějček <dmatej@xxxxxxxxx> wrote:Hi,
I agree with this idea, btw the SerializedView should die too => then nearly all methods in StateManager will be affected.I'm curious if someone used that in last years.Me too. In theory it's not such a bad idea, as it makes the back button work really correctly. Essentially without serialised state on server you only store references, and those references point to the current state. This *may* lead to surprises when you use the back button, expect the previous state, but actually get the current one.That said, the difference is obscure in many cases and the bizarre amount of overhead rarely if ever worth it (in my experience).Kind regards,Arjan Tijms_______________________________________________
Have a nice day,David Matějček.
On 01. 09. 21 14:15, arjan tijms wrote:
Hi,
We discussed removing all or most deprecated things from Faces before. One particular class we did not explicitly discuss is jakarta.faces.application.StateManager
For instance:
* @deprecated this has been replaced by {@link #saveView}. The default implementation calls <code>saveView</code> and
* inspects the return. If the return is an <code>Object []</code>, it casts the result to an <code>Object []</code>
* wrapping the first and second elements in an instance of {@link SerializedView}, which it then returns. Otherwise, it
* returns <code>null</code>
*
*/
@Deprecated
public SerializedView saveSerializedView(FacesContext context) {
If nobody objects I like to remove these as well.
Thoughts?
Kind regards,Arjan Tijms
_______________________________________________ faces-dev mailing list faces-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/faces-dev
faces-dev mailing list
faces-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/faces-dev