[
https://jira.jboss.org/jira/browse/JBSEAM-4236?page=com.atlassian.jira.pl...
]
Dan Allen commented on JBSEAM-4236:
-----------------------------------
You are certainly correct in that information from the URL is being dropped. However, you
do realize that information after the # is not the same as request parameters. That
section of the URL is consider the anchor and I don't think (but I could be wrong) it
was ever being preserved. So this is more of a feature request that the anchor be
preserved. That's a reasonable request.
CLONE -captureCurrentView on redirect should capture all request
parameters
---------------------------------------------------------------------------
Key: JBSEAM-4236
URL:
https://jira.jboss.org/jira/browse/JBSEAM-4236
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.2.GA
Environment: Win XP
Reporter: Paul Chan
Assignee: Dan Allen
Fix For: 2.2.0.CR1
Original Estimate: 1 hour
Remaining Estimate: 1 hour
I have tested this fix in 2.1.2 and it is still not working. Here is my test case:
../mydomain/test.seam?cmid=10#menu:test_view&tab:test1
Only cmid=10 is carried over after i login. Anything after the # sign is not carried
over to the new page. It seems to me that when the page was redirected to the login page
the parametes are carried over, but as soon as i enter the login name and password and I
was redirected to the original page all the parameters after the # sign are lost.
===============================================================
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:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira