]
Dan Allen resolved JBSEAM-4066.
-------------------------------
Resolution: Done
captureCurrentView on redirect should capture all request parameters
--------------------------------------------------------------------
Key: JBSEAM-4066
URL:
https://jira.jboss.org/jira/browse/JBSEAM-4066
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.1.GA
Reporter: Dan Allen
Assignee: Dan Allen
Fix For: 2.2.0.CR1
Attachments: JBSEAM-4066-trunk-v1.txt
Original Estimate: 1 hour
Remaining Estimate: 1 hour
When the captureCurrentRequest() method was deprecated and replaced by
captureCurrentView(), the behavior changed such that page parameters were being saved
instead of request parameters. I'm fine with the idea of preserving page parameters
based on how they were bound to the model on the way into the page, but I also think that
arbitrary request parameters need to be captured. Otherwise, the redirect back to the
current view will in many cases be incomplete and thus fail. The logic I propose is to
capture the request parameters and then override the values with the values from the page
parameters (giving page parameters the precedence).
However, long term, we should also consider the fact that multi-value parameters are not
being preserved. Likely they should be captured as well, but there is a lack of
infrastructure to support them.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: