ADF Question: call javascript function from backing bean?

Question

Hi all,
I am running JDeveloper 10.1.3.3 with ADF BC.
Heres my situation:
I have a table, and after inserting a new row, then committing, I want to call a javascript function. I tried using the onkeyup javascript to force a click of the save button, and then call my function after that. However, I really only want the second function to be called AFTER the commit has occurred.
I have tried putting a setTimeout on the second function, but this never executes then. Is there some way that I can call the second javascript function from the backing bean? Is there a better workaround for this? Here is some code:
        function submitCreate(e) {
            var _event = (window.event) ? event : e;
            var KeyID = _event.keyCode;
            switch (KeyID)
                case 13:
                    document.getElementById("form1:tvoTable:commitButton").onclick();
                    doAjax();
                    break;
        function doAjax() {
            var item = document.getElementById("form1:inputText3").innerHTML;
            getAjax(item, "FULL");
        }Thanks,
Heather

Answer 1

Maybe try adding an af:script block in your jsp as a partial target in your backing bean when you commit to the database? We are doing something similar when we get a tab DisclosureEvent but the principle should be the same.
In our jsp we have:
<af:script id="scriptID" text="alert('javascript here');"/>
In the backing bean we have:
method(DisclosureEvent de) {
// get a component somehow or the component, we get it from the disclosure event
// but you could use a binding also. if you don't have the exact script element you need
// to find it like we do below.
UIComponent c = de.getComponent();
// Find our real script component
UIComponent target = c.findComponent(":scriptID");
// get the adf context
AdfFacesContext adfContext = AdfFacesContext.getCurrentInstance();
// add the script as a partial target.
if(target != null) {
adfContext.addPartialTarget(target);
This relies on PPR though, which you may not be doing. If you are navigating to a new page you could set an indication in a backing bean and then access that in an <af:script> block in the new page or even generate the Javascript you want depending on your logic and access all of it via an EL binding on the af:script tag:
<af:script id="scriptID" text="#{bbean.generatedScript}"/>
Hope this helps!
Steve