Why is getDBTransaction().createPreparedStatement not recoginzed even after importing ApplicationModuleImpl?

Question

Hi everyone,
The code below compiles fine from my ServicesAMImpl class (which extends ApplicationModuleImpl). But, when I move this to a "common" class, the code below is not found even when I import the ApplicationModuleImpl class.
    protected void callStoredProcedure(String statement,
                                       Object[] bindVariables) {
        PreparedStatement preparedStatement = null;
        try {
            // 1. Create a JDBC PreparedStatement.
            preparedStatement =
                    getDBTransaction().createPreparedStatement("begin " +
                                                               statement +
                                                               "end; ", 0);
            if (bindVariables != null) {
                // 2. Loop over values (if any) for the bind variables.
                for (int i = 0; i < bindVariables.length; i++) {
                    // 3. Set the value of each bind variable in the statement.
                    preparedStatement.setObject(i + 1, bindVariables[i]);
            // 4. Execute the statement.
            preparedStatement.executeUpdate();
        } catch (SQLException e) {
            throw new JboException(e);
        } finally {
            if (preparedStatement != null) {
                try {
                    // 5. Close the statement.
                    preparedStatement.close();
                } catch (SQLException e) {
                    System.out.println("Exception in callStoredProcedure(" +
                                       "String statement, " +
                                       "Object[] bindVariables): " + e);
                    e.printStackTrace();
James

Answer 1

James,
This is simple java. The method you have problems with, getDBTransaction, is a method which is implemented in the application module implementation class. When you move the method into a common class you move it outside of the application module and the getDBTransaction is not reachable.
As only the application module handles transactions it doesn't make sense to move your method outside the application module.
Timo