Alternative Application Module Coding Style

Question

I want to preface this post with the fact that I'm relatively new to the OA Framework, but not general OO concepts.
Typically you'd see an application module with this structure:
public class testAMImpl extends OAApplicationModuleImpl
   * This is the default constructor (do not remove)
  public testAMImpl()
   * Sample main for debugging Business Components code using the tester.
  public static void main(String[] args)
    launchTester("oacle.apps.test.server", "testAMLocal");
   * Container's getter for SomeVO1
  public SomeVOImpl getSomeVO1()
    return (SomeVOImpl)findViewObject("SomeVO1");
  public void runCheck()
     // Code Here
}As you can see there is a public function to return the view object, and run a method. Also note that the AM extends the OAApplicationModuleImpl class. Typically to invoke a method one would have to call am.invokeMethod("runCheck").
What about coding the AM like this instead:
public class testAMImpl extends OAApplicationModuleImpl implements oracle.apps.test.testAM
   * This is the default constructor (do not remove)
  public testAMImpl()
   * Sample main for debugging Business Components code using the tester.
  public static void main(String[] args)
    launchTester("oacle.apps.test.server", "testAMLocal");
   * Container's getter for SomeVO1
  private SomeVOImpl getSomeVO1()
    return (SomeVOImpl)findViewObject("SomeVO1");
  public void runCheck()
     // Code Here
}I would think that this would be a more ideal approach for a couple of reasons:
1. The client methods can be exported (e.g. runCheck()) and this have compile time checks vice run time.
2. Client can call the method via am.runCheck() vice am.invokeMethod("runCheck")
3. One can make the "getVO" methods private so you prevent the client from calling these methods, which it shouldn't be doing anyways.
I do realize that in this current example the client could still invoke the am.findViewObject method.
Thanks!

Answer 1

No comments? : )