javaserverfaces-spec-public
  1. javaserverfaces-spec-public
  2. JAVASERVERFACES_SPEC_PUBLIC-698

view-param element should be redirect-param in navigation rules

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: 2.0 Rev a
    • Component/s: Navigation
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      698
    • Status Whiteboard:
      Hide

      cat1 schema changelog

      Show
      cat1 schema changelog

      Description

      The <view-param> element that was introduced as a child of the <redirect>
      element was supposed to be called <redirect-param>. Unfortunately, something got
      lost in translation and the terminology for "view parameters" got mixed up with
      redirect parameters.

      I'll explain the difference. A view parameter is a mapping between a request
      parameter and a bean property and is associated with a particular view ID. If
      you are linking or redirecting to that view ID, you can have those mappings run
      in reverse to build a query string. This is activated with the "include view
      parameters" switch on the link (UIOutcomeTarget) component or <redirect> element.

      A redirect parameter in the navigation is equivalent to an <f:param> on a button
      or link. It is a manual setting, which may (or may not) override the value of a
      view parameter. A perfect example is when you want to create a link to the
      previous page of a paginated list. You manually override "page" so that it is
      one less than the current page. <f:param name="page" value="#

      {nav.page - 1}

      "/>

      <view-param> has no business being a child of <redirect> and should be renamed
      to <redirect-param>.

        Activity

        Hide
        mojavelinux added a comment -

        A 2.0 issue.

        Show
        mojavelinux added a comment - A 2.0 issue.
        Hide
        mojavelinux added a comment -

        Update milestone to 2.1 (really 2.0 MR1)

        Show
        mojavelinux added a comment - Update milestone to 2.1 (really 2.0 MR1)
        Hide
        mojavelinux added a comment -

        Update target milestone to 2.0 Rev a

        Show
        mojavelinux added a comment - Update target milestone to 2.0 Rev a
        Hide
        Ed Burns added a comment -

        cat1

        Show
        Ed Burns added a comment - cat1
        Hide
        Ed Burns added a comment -

        schema

        Show
        Ed Burns added a comment - schema
        Hide
        Ed Burns added a comment -

        https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=698

        Include deprecation text on <redirect><view-param> element.

        https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=744

        • integrationWithFacelets.fm

        Section 10.3.2. Correct xref to point to section in appendix that
        includes the facelet taglib schema.

        • appendixA-metadata.fm

        To ease migration for Facelet taglibraries declared using pre-JSF 2.0
        versions of Facelets, implementations must support loading facelet
        taglibrary files that conform to the pre-JSF 2.0 Facelets DTD. Per DTD
        conventions, Facelet taglibrary files declare conformance to this DTD
        by including text similar to the following in at the top of their
        declaring file.

        <!DOCTYPE facelet-taglib PUBLIC
        "-//Sun Microsystems, Inc.//DTD Facelet Taglib 1.0//EN"
        "http://java.sun.com/dtd/facelet-taglib_1_0.dtd">

        Use of this DTD is officially deprecated. This DTD is included for
        reference in Section 1.2.1 "Deprecated DTD for Facelet Taglibraries
        Used by Versions of Facelets Prior to JSF 2.0". It is expected that
        proper JSF 2.0 Facelet Taglibraries will declare conformance to the
        following schema, rather than the deprecated DTD

        https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=588

        • jsf-api/doc/standard-html-renderkit-base.xml

        insert <p> around text for h:link and h:button

        https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=639

        • jsf-ri/conf/share/facelets_jsf_core.tld

        change "name" to "type" on description of f:event tag

        https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=509

        • jsf-ri/conf/share/jstl-core.taglib.xml
        • jsf-ri/conf/share/jstl-core.tld

        Declare that the old, incorrect, Facelets decaration of the uri for
        the JSTL Core taglib be honored, as well as the new, correct one.

        https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=673

        • jsf-api/doc/standard-html-renderkit-base.xml

        Clarify what should happen if the target attribute is not specified.

        https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=642

        • javascriptAPI.fm

        table 14.4.1, change responseTxt to responseText

        reorder rows in table 14.3

        make use case for event listeners be correct.

        https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=635

        • userInterfaceComponentModel.fm

        3.5.3, 3.5.6.1: remove references to UInput.encodeEnd(). Not for a
        very long time has this method been used to instigate validation.

        https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=740

        • requestProcessingLifecycle.fm
        • 2.6.1.3 Tighten spec for the localePrefix, libraryName, and
          resourceVersion segments of the resource identifier
        Show
        Ed Burns added a comment - https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=698 Include deprecation text on <redirect><view-param> element. https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=744 integrationWithFacelets.fm Section 10.3.2. Correct xref to point to section in appendix that includes the facelet taglib schema. appendixA-metadata.fm To ease migration for Facelet taglibraries declared using pre-JSF 2.0 versions of Facelets, implementations must support loading facelet taglibrary files that conform to the pre-JSF 2.0 Facelets DTD. Per DTD conventions, Facelet taglibrary files declare conformance to this DTD by including text similar to the following in at the top of their declaring file. <!DOCTYPE facelet-taglib PUBLIC "-//Sun Microsystems, Inc.//DTD Facelet Taglib 1.0//EN" "http://java.sun.com/dtd/facelet-taglib_1_0.dtd"> Use of this DTD is officially deprecated. This DTD is included for reference in Section 1.2.1 "Deprecated DTD for Facelet Taglibraries Used by Versions of Facelets Prior to JSF 2.0". It is expected that proper JSF 2.0 Facelet Taglibraries will declare conformance to the following schema, rather than the deprecated DTD https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=588 jsf-api/doc/standard-html-renderkit-base.xml insert <p> around text for h:link and h:button https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=639 jsf-ri/conf/share/facelets_jsf_core.tld change "name" to "type" on description of f:event tag https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=509 jsf-ri/conf/share/jstl-core.taglib.xml jsf-ri/conf/share/jstl-core.tld Declare that the old, incorrect, Facelets decaration of the uri for the JSTL Core taglib be honored, as well as the new, correct one. https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=673 jsf-api/doc/standard-html-renderkit-base.xml Clarify what should happen if the target attribute is not specified. https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=642 javascriptAPI.fm table 14.4.1, change responseTxt to responseText reorder rows in table 14.3 make use case for event listeners be correct. https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=635 userInterfaceComponentModel.fm 3.5.3, 3.5.6.1: remove references to UInput.encodeEnd(). Not for a very long time has this method been used to instigate validation. https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=740 requestProcessingLifecycle.fm 2.6.1.3 Tighten spec for the localePrefix, libraryName, and resourceVersion segments of the resource identifier
        Hide
        Ed Burns added a comment -

        These are valid 2.0 Rev a issues

        Show
        Ed Burns added a comment - These are valid 2.0 Rev a issues
        Hide
        rogerk added a comment -

        changelog

        Show
        rogerk added a comment - changelog
        Hide
        Manfred Riem added a comment -

        Closing resolved issue out

        Show
        Manfred Riem added a comment - Closing resolved issue out

          People

          • Assignee:
            javaserverfowner
            Reporter:
            mojavelinux
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: