[
http://jira.jboss.com/jira/browse/JBSEAM-2469?page=comments#action_12414260 ]
Stephen Friedrich commented on JBSEAM-2469:
-------------------------------------------
Thanks again for the explanation and your patience.
I think it would really be a better solution to utilize Seam's capability of having
state surviving a redirect.
After all that is what seam also does for FacesMessages, right?
If this is implemented in the easy way, by making it dependent on the postback/initial
request distinction it would be the source of confusion and potential bugs.
You would have to be much more familiar with technical details to see when the option
might be useful.
Also I think redirect-after-post is a common idiom, so even if you know about these
technical details, you will simply not be able to use the solution.
add postback flag to page actions
---------------------------------
Key: JBSEAM-2469
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2469
Project: Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.0.1.CR1
Reporter: Dan Allen
Assigned To: Dan Allen
Fix For: 2.1.0.BETA2
Original Estimate: 1 hour
Remaining Estimate: 1 hour
Page actions are incredibly useful, but sometimes they can get in the way during a
postback. I would like to see a postback attribute added to the <action> tag that
can be used to disable the action on postback. It's possible using a conditional, but
it is ugly and a lot of typing.
Here is the logic that would go into Pages.java
private boolean isPostBack(FacesContext facesContext)
{
return facesContext.getExternalContext().getRequestParameterMap().
containsKey(ResponseStateManager.VIEW_STATE_PARAM);
}
The conditional alternative would be:
<action execute="#{component.action}" if="#{empty
param['javax.faces.ViewState']}"/>
--
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