How to show modal panel or call bean method in commandButton

[nille]

Hi everybody,

I have a question regarding the combination of using JS in a a4j:commandButton and executing an action. There is the following scenario: If the commandButton is clicked either a modalPanel should be displayed or a bean method should be called. For now I have the following elements in use.

{code:xml}
<a4j:jsFunction name="executeSaveAction"  eventsQueue="ajaxQueue" action="#{myBean.save()}" 
     reRender="buttonArea"/>

<rich:messages id="messages" errorClass="messageError" infoClass="messageInfo" warnClass="messageWarn"/>

<a4j:commandButton styleClass="save-button" id="save" value="save" ajaxSingle="true"
     type="submit" eventsQueue="ajaxQueue" oncomplete="Javascript: window.location.hash='#top';"
     onclick="#{(myBean.location or myBean.employees) ?  'Richfaces.showModalPanel(\'modalPanelSaveOrCancel\');'  :'executeSaveAction;'}"/>
<ui:insert name="modalPanelSaveOrCancel">

    <ui:include src="modalPanelSaveOrCancel.xhtml"/>
</ui:insert>
{code}

The problem with this solution is that two ajay requests are generated, one for the commandButton and another one for the a4j:Function. The bean method creates a info message which should be displayed after the method ends. This works, but only as long as the second ajax request ends. Than the message disappears. In the 'onclick' attribute of the commandButton only JS is allowed, right? Therefore I used the a4j:function to call the bean method from within the 'onclick' attribute.

My question is: how can I get rid of the second ajax request?

Thanks in advance,

Cheers,
nille

[nille]

If no one has an idea I think I have to use two commandButtons (one with the onclick event showing the modal panel and the other with the action attribute calling the bean method)  rendered alternatively.

Kind regards,

nille

[ilya_shaikovsky]

If no one has an idea I think I have to use two commandButtons (one with the onclick event showing the modal panel and the other with the action attribute calling the bean method)  rendered alternatively.

that's way looks better for me. (at least easier to maintain)

But if you prefer first one - it's easy to correct the problem with duplicated requests. just add return  false; stateent after calls to modal or jsFunction.

[nille]

Thanks,

that is exactly what I was searching for. =)

I'll try both ways and choose than.