Reverse action and onclick on commandButton.

Question

Hi, my question is about this:
In jspx.
<af:commandButton text="Report" blocking="false"
action="#{myOwnBean.report_Action}"
onclick="#{myOwnBean.chainWeb}"/>
I want execute action first, and then onclick in second place.
Are there some way to do this? And, how is this done?
Please, if you could give me some examples.
Thank you very much.
In myOwnBean. It changes "chainWeb", the chain may vary, that's why I want to do the opposite.
private String chainWeb;
public void report_Action() {
// In this place I want create a set of dynamic URLs.
chainWeb="window.open(\"http://www.google.com\" , \"window1\" , \"width=120,height=300,scrollbars=NO\");window.open(\"http://www.oracle.com\" , \"window2\" , \"width=120,height=300,scrollbars=NO\");parent.parent.close();";
}

Answer 1

What about this?:
<af:commandButton text="Report" blocking="false" onclick="#{myOwnBean.chainWeb}"/>Then in the bean do this?:
public MyOwnBean {
  private String chainWeb;
  public String getChainWeb() {
    chainWeb = "window.open(\"http://www.google.com\" , \"window1\" , \"width=120,height=300,scrollbars=NO\");window.open(\"http://www.oracle.com\" , \"window2\" , \"width=120,height=300,scrollbars=NO\");parent.parent.close();"
    // or alternatively call any other bean code to work out what you want to set chainWeb to.
    return chainWeb;
}... in that manner the work done by your original report_action method is done in the getChainWeb method. Is that suitable?
As you know the action attribute of the commandButton is designed for returning navigation rules as calculated on the server after the user submits the page back to the midtier. In turn onclick is a client side JavaScript event and will always fire in the browser before the action attribute is processed by the mid-tier.
A further issue I see is that the EL expression for the onclick JavaScript attribute will be evaluated when the page is fetched, not when the user onclicks. As such if you want the result of chainWeb to be dependent on values on the current screen, you'll need to know how to extract them in your JavaScript from the DOM, as separate to fetching them from a bean or binding component.
CM.