MyFaces Core
  1. MyFaces Core
  2. MYFACES-3335

jsf.getViewState() create a new _AjaxUtils object, but it is singleton

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.10, 2.1.4
    • Component/s: JSR-314
    • Labels:
      None

      Description

      jsf.getViewState() create a new _AjaxUtils object, but it is singleton. It should just grab the object, because when jsf.js is loaded, this instance is created

      1. MYFACES-3335-1.patch
        0.7 kB
        Leonardo Uribe

        Activity

        Leonardo Uribe created issue -
        Leonardo Uribe made changes -
        Field Original Value New Value
        Attachment MYFACES-3335-1.patch [ 12496771 ]
        Leonardo Uribe made changes -
        Status Open [ 1 ] Patch Available [ 10002 ]
        Hide
        Werner Punz added a comment -

        Thanks Leo, I have missed this at my refactoring, you are right, it has been a singleton since my last refactoring and a new is totally out of scope there.

        Show
        Werner Punz added a comment - Thanks Leo, I have missed this at my refactoring, you are right, it has been a singleton since my last refactoring and a new is totally out of scope there.
        Hide
        Werner Punz added a comment -

        Ok there is more to it, I rely on the standard error handlers in the encodesubmittablefields, I have to change that, this could be related to: https://issues.apache.org/jira/browse/MYFACES-3334 because if you call encode submittable fields and raise an error by issuing it wrongly, you will run into the issue of not having an error handler there because there is no context available which hosts the error handlers.

        This needs to be fixed.

        Show
        Werner Punz added a comment - Ok there is more to it, I rely on the standard error handlers in the encodesubmittablefields, I have to change that, this could be related to: https://issues.apache.org/jira/browse/MYFACES-3334 because if you call encode submittable fields and raise an error by issuing it wrongly, you will run into the issue of not having an error handler there because there is no context available which hosts the error handlers. This needs to be fixed.
        Hide
        Werner Punz added a comment -

        Ok this bug gave me the incentive to rework the entire viewstate subystem

        Show
        Werner Punz added a comment - Ok this bug gave me the incentive to rework the entire viewstate subystem
        Werner Punz made changes -
        Status Patch Available [ 10002 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Leonardo Uribe made changes -
        Fix Version/s 2.1.4 [ 12317868 ]
        Fix Version/s 2.0.10 [ 12317870 ]
        Leonardo Uribe made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Patch Available Patch Available
        57s 1 Leonardo Uribe 27/Sep/11 17:40
        Patch Available Patch Available Resolved Resolved
        1d 16h 5m 1 Werner Punz 29/Sep/11 09:46
        Resolved Resolved Closed Closed
        130d 13h 41m 1 Leonardo Uribe 06/Feb/12 23:27

          People

          • Assignee:
            Leonardo Uribe
            Reporter:
            Leonardo Uribe
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development