ADF: Configuration.createRootApplicationModule() generates bc4j.xcfg error

Question

I am using JDeveloper 11.1.1.5 to create a web service which performs mathematical calculations based on a varying number of inputs. Some of the inputs serve as criteria for querying DB tables to obtain static numerical values. This static data is then plugged into a formula to produce the output of the service. My approach is to build an ADF application with 2 projects: a "service" project which contains a java-based web service created using the "Create Java Web Service From WSDL" wizard; a "model" project that consists of an Application Module and some read-only SQL query-based views as it's Data Model. Additionally, the AppModule.xml editing tool was used to generate an AppModuleImpl.java class and it's associated client interface classes. The intent is to instantiate the App Module from the service project and call a custom method to perform the required DB lookup. The code to do this looks as follows:
In service implementation class (com.util.formula.service.FormulaCalculationServiceImpl.calculateLicensingFee):
import com.sesac.formula.lkup.client.AppModuleClient; //generated by App Module Java Class wizard
import oracle.jbo.client.Configuration;
AppModuleClient lkup;
try {
lkup = (AppModuleClient)Configuration.createRootApplicationModule("com.util.formula.lkup.AppModule", "AppModuleLocal");
} catch (Exception e) {
e.printStackTrace();
The following exception is always thrown:
oracle.jbo.ConfigException: JBO-33001: Configuration file /com/util/formula/lkup/common/bc4j.xcfg is not found in the classpath.
     at oracle.jbo.client.Configuration.loadFromClassPath(Configuration.java:467)
     at oracle.jbo.common.ampool.PoolMgr.loadConfiguration(PoolMgr.java:600)
     at oracle.jbo.common.ampool.PoolMgr.findPool(PoolMgr.java:526)
     at oracle.jbo.client.Configuration.createRootApplicationModule(Configuration.java:1505)
     at oracle.jbo.client.Configuration.createRootApplicationModule(Configuration.java:1482)
     at com.util.formula.service.FormulaCalculationServiceImpl.calculateLicensingFee(FormulaCalculationServiceImpl.java:28)
... more
The service project Properties -> Dependencies specifies a dependency on the model project. I have tried making the dependency on both the Build Output and on the BC_Common.jar generated by the model project - neither works. I have exploded the the .war generated for the service project and verified that bc4j.xcfg does indeed exist at the classpath location described in the error message. It also exists in the BC_Common.jar at the correct location.
I also tried the following alternative approach to instantiating the App Module:
import com.util.formula.model.client.AppModuleClient;
import oracle.adf.model.BindingContext;
import oracle.jbo.uicli.binding.JUApplication;
AppModuleClient lkup;
try {
BindingContext bc = oracle.adf.model.BindingContext.getCurrent();
JUApplication japp = (JUApplication)bc.getCurrentBindingsEntry().get("AppModuleDataControl");
lkup = (AppModuleClient)japp.getApplicationModule();
} catch (Exception e) {
e.printStackTrace();
In this case, BindingContext.getCurrent() returns null.
The same App Module that I'm unable to instantiate as above runs fine in Oracle Business Component Browser. I chose this approach because I have been using App Modules in the same development environment when they were directly bound to UI's and Service Interfaces with good success and I liked the features it provided. I've spent way too much time beating on this and searching every forum I could find. The example for using Configuration.createRootApplicationModule() came right out of Chapter 9, Section 10 of Oracle Fusion Middleware - Fusion Developer's Guide for Oracle Application Development Framework (11g Release 1). Any ideas would be greatly appreciated.
Thanks,
Tom

Answer 1

I guess you get a new connection this way. If you have an ApplicationModule you can get the internal connection this way    public Connection getCurrentConnection(ApplicationModule aApp)
        Statement st = null;
        try
            // create Dummy Statement to get the connection
            st = aApp.getDBTransaction().createStatement(0);
            return st.getConnection();
        catch (SQLException s)
           // Log some message here and do something
        finally
            // close statement
            if (st != null)
                try
                    st.close();
                catch (SQLException s2)
    }Timo