Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
eclipse-faces-bot opened this issue Dec 13, 2009 · 14 comments
Closed

Comments

@eclipse-faces-bot
Copy link

The element that was introduced as a child of the
element was supposed to be called . 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 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}

"/>

has no business being a child of and should be renamed
to .

Environment

Operating System: All
Platform: All

Affected Versions

[2.0]

@eclipse-faces-bot
Copy link
Author

@glassfishrobot Commented
Reported by mojavelinux

@eclipse-faces-bot
Copy link
Author

@glassfishrobot Commented
Was assigned to javaserverfowner

@eclipse-faces-bot
Copy link
Author

@glassfishrobot Commented
mojavelinux said:
A 2.0 issue.

@eclipse-faces-bot
Copy link
Author

@glassfishrobot Commented
mojavelinux said:
Update milestone to 2.1 (really 2.0 MR1)

@eclipse-faces-bot
Copy link
Author

@glassfishrobot Commented
mojavelinux said:
Update target milestone to 2.0 Rev a

@eclipse-faces-bot
Copy link
Author

@glassfishrobot Commented
@edburns said:
cat1

@eclipse-faces-bot
Copy link
Author

@glassfishrobot Commented
@edburns said:
schema

@eclipse-faces-bot
Copy link
Author

@glassfishrobot Commented
@edburns said:
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=698

Include deprecation text on 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.

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

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

@eclipse-faces-bot
Copy link
Author

@glassfishrobot Commented
@edburns said:
These are valid 2.0 Rev a issues

@eclipse-faces-bot
Copy link
Author

@glassfishrobot Commented
rogerk said:
changelog

@eclipse-faces-bot
Copy link
Author

@glassfishrobot Commented
Marked as fixed on Tuesday, June 22nd 2010, 1:22:20 am

@eclipse-faces-bot
Copy link
Author

@glassfishrobot Commented
@manfredriem said:
Closing resolved issue out

@eclipse-faces-bot
Copy link
Author

@glassfishrobot Commented
This issue was imported from java.net JIRA JAVASERVERFACES_SPEC_PUBLIC-698

@eclipse-faces-bot
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants