1. Tapestry
  2. TAPESTRY-1368

The @ApplicationState annotation should be capable of enhancing a boolean field to indicate whether the state object already exists


    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0
    • Fix Version/s: 5.0.4
    • Component/s: tapestry-core
    • Labels:


      Currently, you can use @ApplicationState to identify a field that can be used to access an Application State Object:

      private MyState _myState;

      However, there's no way to determine if the state object already exists; checking it (_myState != null) will force the object (and, perhaps, the session) into existence. A kind of "heisenbug".

      What could be done is to look for a related field of type boolean, with "Exists" appended (i.e., "_myStateExists"). This boolean flag could be enhanced to check to see if the related ASO exists or not, without creating it.


        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Closed Closed
        13d 16h 26m 1 Howard M. Lewis Ship 30/Mar/07 15:25
        Mark Thomas made changes -
        Workflow Default workflow, editable Closed status [ 12569203 ] jira [ 12592125 ]
        Mark Thomas made changes -
        Workflow jira [ 12399779 ] Default workflow, editable Closed status [ 12569203 ]
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Status Open [ 1 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        Assignee Howard M. Lewis Ship [ hlship ]
        Fix Version/s 5.0.4 [ 12312381 ]
        Howard M. Lewis Ship created issue -


          • Assignee:
            Howard M. Lewis Ship
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            0 Start watching this issue


            • Created: