Skip to main content

Dynamic datasource selection/ swapping ADF

Just did this for a quick poc so pleased adapt this code as is is not production suitable.

1) Create a factory

package za.poc;
import oracle.jbo.server.DatabaseTransactionFactory;

public class CustomDatabaseTransactionFactory extends
 DatabaseTransactionFactory {
    public CustomDatabaseTransactionFactory() {
        super();
    }
    
    public oracle.jbo.server.DBTransactionImpl2 create() {
      return new CustomTransaction();
    }
}


2) Create new Transaction class
package za.poc;

import oracle.adf.share.ADFContext;
import oracle.jbo.server.DBTransactionImpl2;

public class CustomTransaction extends DBTransactionImpl2 {
  public CustomTransaction() {
    super();
  }

  public void connectToDataSource(java.util.Hashtable p1, java.lang.String p2, java.lang.String p3,
    java.lang.String p4, boolean p5) {
    String userName = (String)ADFContext.getCurrent()
      .getSessionScope().get("USER_NAME");
      if (userName != null) {
          if ("test".equalsIgnoreCase(userName) ) {
            p2 = "jdbc/testDS";
          }
      }
       super.connectToDataSource(p1, p2, p3, p4, p5);
  }
}

3) Override AM TransactionFactory property to your newly created class.

4) set the session value on login.
session.setAttribute("USER_NAME", "test");

See this blog post for an alternative (probably better)
http://jobinesh.blogspot.com/2011/04/modifying-application-modules-jdbc.html

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

MANIFEST.MF merge JDeveloper for an executable jar

Goto your project > properties. Then click on deployment in the menu. Edit or add a jar deployment profile. Fill in the details under jar options (select Include manifest and give it a main class name) Also remember that the merge functionality only works with a BLANK line at the end of the merge file. REALLY this caught me. My merge file contents: Class-Path: commons-codec-1.3.jar [...empty line here CRLF...]