Tapestry 5
  1. Tapestry 5
  2. TAP5-1024

Submit component should allow return values from event handler methods triggered by its event


    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.2.0
    • Fix Version/s: 5.2.0
    • Component/s: tapestry-core
    • Labels:


      Currently, the Submit component (and friends, such as LinkSubmit) fire an event that does not support return values.

      It should be capable of returning any "navigational result", just like most events (such as all those fired by the Form itself).

      Ideally, this would be a case of sharing the ComponentEventResultProcessor instance used by the Form itself (as an environmental).


        Howard M. Lewis Ship created issue -
        Howard M. Lewis Ship made changes -
        Field Original Value New Value
        Assignee Howard M. Lewis Ship [ hlship ]
        Howard M. Lewis Ship made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Howard M. Lewis Ship made changes -
        Status In Progress [ 3 ] Closed [ 6 ]
        Fix Version/s 5.2.0 [ 12314122 ]
        Resolution Fixed [ 1 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        5s 1 Howard M. Lewis Ship 20/Feb/10 01:10
        In Progress In Progress Closed Closed
        2d 17h 59m 1 Howard M. Lewis Ship 22/Feb/10 19:09


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


            • Created: