Skip to main content

Double click call button my way

1) In your jsff page add the following tag:
<f:verbatim><input id="buttonId" type="hidden" /><verbatim>
1.1) Also add the following to the tag you want to double click:
<af:clientListener method="executeButton" type="dblClick"/>

2) Add the following javascript:
function executeButton(event) {
  var tbl = event.getSource();
  if (tbl.getSelectedRowKeys() != null) {
    var btn = 
      AdfPage.PAGE.findComponent(document.getElementById("buttonId").value);
    if (btn != null) {
      AdfActionEvent.queue(btn, false);
    }
    event.cancel();
  }
}

3) Bind your button to a backing bean:

private RichCommandToolbarButton button;
  public void setButton(RichCommandToolbarButton button){
    FacesContext fctx = FacesContext.getCurrentInstance();
    Service.getRenderKitService(fctx, 
      ExtendedRenderKitService.class).addScript(fctx, 
      "document.getElementById(\"buttonId\").value = '"
      + editButton.getClientId(FacesContext.getCurrentInstance())
      + "'");
    this.button = button;
  }

  public RichCommandToolbarButton getButton(){
    return button;
  }

Comments

Popular posts from this blog

ADF Encountered deferred syntax #{ in template text.

OracleJSP error: oracle.jsp.parse.JspParseException:  Error: Encountered deferred syntax #{ in template text.  If intended as a literal, escape it or set directive  deferredSyntaxAllowedAsLiteral This normally happens when you have some tag lib dependancy problems but this was  not the case for me... My problem: For some reason my model project had web stuff in it(public html etc)  so I had to remove the public html stuff from my project and manually edit the Model.jpr project file and remove the tag lib entries at the bottom o the file. Go figure.    

JBO-25013: TooManyObjectsException

oracle.jbo.TooManyObjectsException: JBO-25013: Too many objects match the primary key oracle.jbo.Key[Key null ]. Ok so for you it may be trying to insert a duplicate record this should explain your problem (also check trigger they could be the cause.) NOTE: You can also try to create a new duplicate EO if you have a page with two VO's using the same EO. This could sort your problems. For me I needed to add a launch listener on my LOV and clear the cache of my vo. LOV <af:inputListOfValues id="NameId" popupTitle="#{bindings.Name.hints.label}" value="#{bindings.RolName1.inputValue}" label="#{bindings.RolName1.hints.label}" model="#{bindings.RolName1.listOfValuesModel}" required="#{bindings.RolName1.hints.mandatory}" columns="#{bindings.RolName1.hints.displayWidth}" shortDesc="#{bindings.RolName1.hints.tooltip}" launchPopupListener="#{backingBeanScope.backingBean.launchPop

OJDeploy: Documentation for the tool

Real DOCS:  http://docs.oracle.com/cd/E26098_01/user.1112/e17455/deploying_apps.htm#OJDUG645 OJDeploy Documentation if you run it from the command line - I keep looking for this so I though I would post it here so I remeber. Oracle JDeveloper Deploy 11.1.2.1.0.6081 Copyright (c) 2003, 2010, Oracle and/or its affiliates. All rights reserved. Usage:   ojdeploy -profile <name> -workspace <jws> [ -project <name> ] [ <options> ]   ojdeploy -buildfile <ojbuild.xml> [ <options> ]   ojdeploy -buildfileschema Arguments:   -profile               the name of the Profile to deploy   -workspace      full path to the JDeveloper Workspace file(.jws)   -project              name of the JDeveloper Project within the .jws where the Profile can be found. If omitted, the Profile is assumed to be in the Workspace.   -buildfile            full path to a build file for batch deploy   -buildfileschema  print XML Schema for the build file