Uploaded image for project: 'Wicket'
  1. Wicket
  2. WICKET-2006

The page set by setReponsePage does not process its own response.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.4-RC1
    • 1.3.6, 1.4-RC2
    • wicket
    • None
    • Any

    Description

      Whenever the HomePage is submitted, it uses

      setResponsePage(new HomePage(xxx)); to open a new page in a new state.

      Whenever the form is submitted, the original page processes the form and thus any components that have changed state (e.g., become visible / invisible) remain in their original state and are not processed properly.

      More technically:
      The browser is viewing page instance X, but the form being processed belongs to the original page instance 0.

      It seems that the page set by setReponsePage does not process its own response.

      Attachments

        1. Wicket-Quickstart.zip
          32 kB
          Martin Terra

        Activity

          People

            jcompagner Johan Compagner
            mmakundi Martin Terra
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 12h
                12h
                Remaining:
                Remaining Estimate - 12h
                12h
                Logged:
                Time Spent - Not Specified
                Not Specified