Wicket
  1. Wicket
  2. WICKET-30

Nice and more practical url scheme

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0 branch (discontinued), 1.3.0-beta1
    • Fix Version/s: 1.3.0-rc1
    • Component/s: wicket
    • Labels:
      None

      Description

      I'd like our urls to be redesigned. Currently, there are lot of issues, such as not preserving bookmarkable urls after action on page or not preserving page state when using ajax on pages with bookmarkable urls.

      We should introducte hybrid urls - urls that would contains both page class and page instance id.
      Example of url of mounted page with hybrid url: /my/page/param1/value1[25]

      When such url is entered, wicket would first try to retrieve page with id 25. If the page is found, it would check whether the class matches with given mount point. If so, it would show the page, otherwise new page instance would be created and the url would be redirected to e.g.
      /my/page/param1/value1[31] (where 31 would be new page instance).

      Also (this would be configurable per page class), after entering bookmarkable url, the browser would be automatically redirected to hybrid url. For instance user enters /my/page and gets immediately rendered to /my/page[4] where 4 is new page instance. The benefit of this would be that ajax changes on page would be persisted after refreshing the page, which is not the case with current bookmarkable urls.

        Activity

        Show
        Matej Knopp added a comment - http://cwiki.apache.org/confluence/display/WICKET/Proposal+of+URL+scheme+for+Wicket+2
        Hide
        Eelco Hillenius added a comment -

        Still thinking about this Matej?

        Show
        Eelco Hillenius added a comment - Still thinking about this Matej?
        Hide
        Johan Compagner added a comment -

        what we also could think about is that we have mounts that are really "static" with that i mean one session has always one instance for that page.

        We could do this if you say it if you mount (extra param)
        or what we could do.. if we get a bookmarkable url request. Then we first check what the active page is in the current pagemap if that is the same class then we just return that one.
        Would this cause big problems??

        I don't think so because there is no backbutton added. (when you do a refresh of the url, the browser already really thinks that that is the current/same page)

        Show
        Johan Compagner added a comment - what we also could think about is that we have mounts that are really "static" with that i mean one session has always one instance for that page. We could do this if you say it if you mount (extra param) or what we could do.. if we get a bookmarkable url request. Then we first check what the active page is in the current pagemap if that is the same class then we just return that one. Would this cause big problems?? I don't think so because there is no backbutton added. (when you do a refresh of the url, the browser already really thinks that that is the current/same page)
        Hide
        Eelco Hillenius added a comment -

        Assigned version (beta 4)

        Show
        Eelco Hillenius added a comment - Assigned version (beta 4)
        Hide
        Matej Knopp added a comment -

        All done for 1.3

        Show
        Matej Knopp added a comment - All done for 1.3

          People

          • Assignee:
            Matej Knopp
            Reporter:
            Matej Knopp
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development