[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2469) add postback flag to page actions
[ http://jira.jboss.com/jira/browse/JBSEAM-2469?page=comments#action_12414249 ]
Stephen Friedrich commented on JBSEAM-2469:
-------------------------------------------
Thanks Dan.
Now, if you were to navigate after a postback, either to the same
page (redirect) or another page, then it ceases to be classified as a postback at that
point.
That was the point I did not understand, but ok, I'll trust you here.
...
Hm, I'd like to understand it, though.
Why is a postback-request suddenly no longer a postback request if it results in rendering
of a new page? AFAICS there is no initial request involved either?!
All my pages have a <redirect> in their navigation rules. Will it work in spite of
that?
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