[
http://jira.jboss.com/jira/browse/JBSEAM-660?page=comments#action_12350962 ]
Giampaolo Tomassoni commented on JBSEAM-660:
--------------------------------------------
Well, no: I'm wrong. Facelets-1.1.11 doesn't fix it. It only better interacts with
a fix I attempted in my app (not the test one I reported).
I'm reporting the problem upstream, but please note I suspect there are ways to
circumvent the problem in Seam. This may be required if upstream I'm told that this
facelets behaviour is by design. After all, a form MAY be submitted by a GET...
Externally switching parameters on a form page backed by "page
parameters" constructs yields erratic behaviour
--------------------------------------------------------------------------------------------------------------
Key: JBSEAM-660
URL:
http://jira.jboss.com/jira/browse/JBSEAM-660
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 1.2.0.BETA1, 1.1.0.GA, 1.1.1.GA, 1.1.5.GA
Environment: JBoss-4.0.5.GA
Reporter: Giampaolo Tomassoni
Assigned To: Gavin King
Attachments: test02.zip
When a form with "page parameters" is shown and then the same page but with new
parameters is attempted by some external action (in example, by manually changing the
parameter values in the browser's navigation bar, the page still holds the previous
parameter values.
This is particularly annoing in frame-based sites, in which a frame is used to
"navigate" on the parameter's space of a form in the right frame.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira