ADF 11g – Invoke a Popup from a Popup

Luc Bors 9
0 0
Read Time:4 Minute, 14 Second

Today I was triggered by a question on the JDeveloper forum about invoking a popup from a backing bean. Actually some time ago I had to build that solution for one of my customers that needed some kind of confirmation to the user that an action invoked in a dialog popup was succesfull. The flow in this solution was more ore less like this: Invoke a dialog popup –> press ok (or cancel) in the dialog –> if ok was pressed, invoke the dialogListener which contains the actual logic to be executed. In case the action is succesfull, show another popup that tells the user “all is well” in all the other cases do something different.


Usually I would add a show popup behaviour to the component from which the popup has to be invoked. However in this case that is not posisble. The invoking component is another popup, and the only triggertypes that are supported for the <af:showpopupbehaviour> are popupClosed, popupOpened and popupOpening.


Available triggers on popup


The popupClosed would be the rigth triggertype to use but saddly this responds to both the OK and to the Cancel button.  It seems that is not possible to differentiate between Ok and Cancel. In case of cancel I don’t want to show the second popup, but show the user the initial page. In case of Ok I need to have control on what happens. To achieve this behaviour  I need to invoke the second popup programmatically.

Lets go with this use case.

First I need the following managed bean configuration for binding some page elements.




This is the code for the default page with the inputText bound to a backing bean named PopupBean.


<?xml version='1.0' encoding='windows-1252'?>
<jsp:root xmlns:jsp="" version="2.1"
  < contentType="text/html;charset=windows-1252"/>
        <af:panelGroupLayout halign="center" valign="middle">
        <af:spacer width="50%" height="100"/>
          <af:commandButton id="justSomeButton" text="Hover Me"
            <af:showPopupBehavior popupId="justSomePopup"
          <af:popup id="justSomePopup">
              <af:dialog title="This is an input dialog">
              <af:inputText value="This is just text"


Add a dialog Listener to the dialog and create a method popupAction in the PopupBean.
<af:dialog dialogListener=”#{PopupBean.popupAction}”>

Add the javascript function that opens the confirmation popup to the page.


 <f:facet name="metaContainer">
                function launchConfirmed() {
                    var popup = AdfPage.PAGE.findComponent("confirmMessage");                     


And finally add the confirmation popup

       <af:popup id="confirmMessage">
            <af:dialog cancelVisible="false"
                       title="This is a confirmation message">
            <af:outputText binding="#{PopupBean.confirmeTypedText}"/>


Now you are ready to invoke the first popup. Run the page and hover the mouse over the button and the  popup will appear. Note that the cancelButton and closeIcon are visible, but using these does not invoke the code in de backing bean.


First popup


After clicking OK on this popup you can do some processing and (if successfull) invoke the confirmation popup.
You will need the following code in the popupAction method.

public void popupAction(DialogEvent dialogEvent) {
     // Do all the processing you need
     // for now just forward the typed text to the outputText in the second popup.
     System.out.println("dialogEvent = " + dialogEvent.getOutcome().toString());
     confirmeTypedText.setValue("the following text was succesfully processed: " +getTypedValue().getValue());
     FacesContext context = FacesContext.getCurrentInstance();
     ExtendedRenderKitService service = (ExtendedRenderKitService)Service.getRenderKitService(context, ExtendedRenderKitService.class);
     service.addScript(context, "launchConfirmed();");


The addScript part in this mehod does the trick. It will add a handle to the javascript funtion that invokes the second popup. Run the page again, invoke the first popup, and click OK. The second popup will now be invoked.


Second popup


Now you have the solution for invoking a popup from a popup or (even better) invoke a popup form a backing bean.





About Post Author

Luc Bors

Luc Bors is Expertise Lead ADF and technical specialist/architect at AMIS, Nieuwegein (The Netherlands). He developed several Workshops and training on ADF and also is an ADF and JHeadstart instructor. Luc is a member of the ADF Methodology group and publishes articles on ADF in oracle technology related magazines, on the AMIS technology blog, (
0 %
0 %
0 %
0 %
0 %
0 %

Average Rating

5 Star
4 Star
3 Star
2 Star
1 Star

9 thoughts on “ADF 11g – Invoke a Popup from a Popup

  1. This is a browser popup and not an ADF Javascript popup. Do you have a good use case for using  afContext.launchDialog ? If you use ADF Javascript popups you have more control on how the popup is rendered, and besides that, popup blockers will not step in and break your app.

  2. Hi,
    I run a popup with afContext.launchDialog, all is ok, but my question is, how can invoke the popup but without close icon in ADF. Thanks.

    Sorry by mi english, i not so god in that, XP.

  3. Why not just use a FacesContext.addMessage(clientId, message) in the dialogListener.

  4. hey
    Can you please tell me where to insert the facet metaContainer?
    Thank you
    PS your source code would be more than helpfull

  5. I tried the above thing. I am getting the below error on browser status bar(!); and the second popup doesn’t open. There is no error in the log.

    ‘AdfPage.PAGE.findComponent(…)’ is null or not an object.
    Although the popup id is there on the jspx page.

  6. It looks like I’ve lost the project with the samplecode somewhere in time. Luckily the codesamples provided in this post should do the trick.

Comments are closed.

Next Post

Bloom Filters, Hierarchical Profiling, Synopses & One pass distinct sampling, jumping the GAPP ... - feast for DBAs (considered harmful..)

  It’s Monday night and a select company of DBAs and Database developers have gathered at AMIS HQ in Nieuwegein for the ‘Looking Back at Hotsos 2009’ session. It is one of those sessions that has a lot of energy, laughter and a wealth of serious content. Four very experienced […]
%d bloggers like this: