Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Hi,

      Kito suggested I submit this as a feature request. The idea is simply to retain the Request URL for postbacks in order to keep state encoded in the Request URL.

      All forms are posted back to the original View ID. But this doesn't tell the whole story because the View ID is not the Request URL and we lose state that is encoded in request parameters or RESTful URL schemes like /app/widgets/300/edit.

      We can fix this fairly easily.

      All we need to do is post back to the original Request URL instead of the View ID and we're done. The forms come out looking like:

      <form action="/app/widgets/WidgetEditor.xhtml?id=300&type=blue">..</form>

      or

      <form action="/app/widgets/300/edit">..</form>

      instead of

      <form action="/app/widgets/WidgetEditor.xhtml"/>..</form>

      I posted an implementation of this scheme at http://www.ninthavenue.com.au/preserving-jsf-request-parameters-and-rest-urls and am using it in production.

        Activity

        Hide
        arjan tijms added a comment -

        JAVASERVERFACES_SPEC_PUBLIC-1175 seems to ask for the same thing.

        Note that we implemented something similar for the o:form component in OmniFaces. The current implementation only includes the view parameters though, not all request parameters (I'll add an option for doing the last thing as well which can optionally be used while this issue is still open).

        Show
        arjan tijms added a comment - JAVASERVERFACES_SPEC_PUBLIC-1175 seems to ask for the same thing. Note that we implemented something similar for the o:form component in OmniFaces. The current implementation only includes the view parameters though, not all request parameters (I'll add an option for doing the last thing as well which can optionally be used while this issue is still open).
        Hide
        arjan tijms added a comment -
        Show
        arjan tijms added a comment - p.s. JAVASERVERFACES_SPEC_PUBLIC-776 and JAVASERVERFACES_SPEC_PUBLIC-1029 are slightly related to this.
        Hide
        Ed Burns added a comment -

        Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.

        Show
        Ed Burns added a comment - Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.
        Hide
        Manfred Riem added a comment -

        Setting priority to Minor

        Show
        Manfred Riem added a comment - Setting priority to Minor

          People

          • Assignee:
            Unassigned
            Reporter:
            rogerkeays
          • Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated: