Issue Details (XML | Word | Printable)

Key: JAVASERVERFACES_SPEC_PUBLIC-359
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Ryan Lubke
Reporter: mfreedma
Votes: 1
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
javaserverfaces-spec-public

PortletBridge issue: Allow EL expression in <to-view-id> of nav rule

Created: 21/May/08 10:01 AM   Updated: 25/Nov/10 06:43 PM   Resolved: 24/Nov/09 07:48 AM
Component/s: Uncategorized
Affects Version/s: 2.0
Fix Version/s: 2.0

Time Tracking:
Not Specified

Environment:

Operating System: All
Platform: All

Issue Links:
Dependency
 

Issuezilla Id: 359
Status Whiteboard:

EGTop5 effort_hard

Tags:
Participants: Ed Burns, mfreedma, rogerk and Ryan Lubke


 Description  « Hide

The portlet model's mechanism for switching views is based on a concept called
portlet Modes. A portlet has distinct Modes (View, Edit, Help). A portlet
typically renders a different view/from a different view context depending on a
mode. Within a given Mode a portlet can extend the model and manage a current
view from within a set of views (for that Mode).

I.e. rather then a typical JSF application having a single set of views that
compose the application, a JSF portlet application has N sets of views where N
is the number of modes supported by the portlet.

Typically when a portlet enters a Mode (from View Mode) they enter at the Modes
default view. However when they exit the Mode by returning to the prior Mode
they just as commonly want to return to the view that was current when they left
the mode as they want to return to that Mode's default view. The portlet
developer is responsible for encoding this navigation directly – though the
underlying environment typically supports navigating to the default view in the
situation that the portlet does nothing other than switch Modes.

The Portlet bridge wants to make it possible for a JSF application to encode
this information in a navigation (rule). It is considering doing the following:

retaining the lastViewId of a Mode being exited and making it available on a
request Attribute (e.g. the request attribute:
javax.portlet.faces.currentViewId.VIEW would have a value of the viewId of the
last view in the last view that was in the portlet VIEW mode. If you wanted the
last mode of the EDIT mode it would be accessed similarly:
javax.portlet.faces.currentViewId.EDIT)

By doing this one could now write the following EL to reference this view:
#{requestScope["javax.portlet.faces.currentViewId.VIEW"]}

To make this useful however, the developer needs to be able to specify this in
the <to-view-id> element of their navigation rule. I.e. Because the portlet use
cases demands that the developer dynamically determine the navigation view when
it triggers/encodes a mode change we would like JSF to support expressing such
dynanism in its navigation rules. As JSF current doesn't specify that the
<to-view-id> element contains/evaluates an EL expression we are seeking this change.



Ed Burns added a comment - 20/Aug/08 08:29 PM
      • Issue 325 has been marked as a duplicate of this issue. ***

rogerk added a comment - 22/Aug/08 08:52 AM

Status Whiteboard


Ed Burns added a comment - 12/Sep/08 04:32 PM

effort_hard


Ed Burns added a comment - 12/Sep/08 04:47 PM

change target_milestone to 2.0


Ed Burns added a comment - 29/Jul/09 01:40 PM

to Ryan


Ed Burns added a comment - 29/Jul/09 01:40 PM

Fixed


Ed Burns added a comment - 24/Nov/09 07:48 AM

Prepare to delete "spec" subcomponent.