[JAVASERVERFACES_SPEC_PUBLIC-484] Specify parameters to include in redirect. Created: 02/Oct/08  Updated: 01/Aug/14  Resolved: 24/Nov/09

Status: Closed
Project: javaserverfaces-spec-public
Component/s: Uncategorized
Affects Version/s: 1.2
Fix Version/s: 2.0

Type: Bug Priority: Major
Reporter: pmuir Assignee: javaserverfowner
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Dependency
blocks JAVASERVERFACES_SPEC_PUBLIC-455 Umbrella for navigation issues Closed
Issuezilla Id: 484
Status Whiteboard:

EGTop5 effort_hard


 Description   

Navigation rules which perform redirects should be able to specify a list of
request parameters to use in the redirect (where the parameter values are
defined using value expressions)



 Comments   
Comment by pmuir [ 02/Oct/08 ]

Blocks 455

Comment by pmuir [ 02/Oct/08 ]

Conversely, any incoming request parameters should be applied to the model using
these mappings. These model updates need to be converted and validated as JSF
would do for POST requests. I would suggest nesting a validator, for example:

<navigation-rule>
<from-action>#

{customerFinder.findByName}

</from-action>
<navigation-case>
<to-view-id>/displayCustomer.xhtml</to-view-id>
<redirect>
<parameter-name>customerId</parameter-name>
<parameter-value>#

{customerFinder.result.id}

</parameter-value>
<validator-id>fooValidator</validator-id>
<converter-id>fooConverter</converter-id>
</redirect>
</navigation-case>
</navigation-rule>

Comment by pmuir [ 10/Oct/08 ]

A JBoss top priority issue issue

Comment by Ed Burns [ 15/Oct/08 ]

Change target milestone to 2.0

Comment by Ed Burns [ 24/Sep/09 ]

fixed in 2.0

Comment by Ed Burns [ 24/Nov/09 ]

Prepare to delete "spec" subcomponent.

Comment by Manfred Riem [ 01/Aug/14 ]

Closing resolved issue out

Generated at Tue Aug 04 18:22:56 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.