Can not access root app module in nested one

Question

I am using Jdeveloper 11g R2 (11.1.2.3) & Weblogic 10.3.5.0
I have a root application module and few nested application modules nested under root one in my ADF application
I have few common methods under root application module Impl class and try to access them in nested Impl classes
like this (This code is in nestedAppModuleImpl class):
RootAppModuleImpl root = (RootAppModuleImpl)someViewObject.getDBTransaction().getRootApplicationModule();
root.doSomething();
when I execute above code this excepton is thrown:
oracle.jbo.server.ApplicationModuleImpl cannot be cast to mypackage.RootAppModuleImpl
Any comment or workaround?
What is the proper solution?
Regards
Mohsen

Answer 1

Mohsen, there is something terribly wrong with your code.
//(This code is in nestedAppModuleImpl class):
RootAppModuleImpl root = (RootAppModuleImpl)someViewObject.getDBTransaction().getRootApplicationModule();
root.doSomething();doesn't make sense. Does doSomething() really return an RootAppModuleImpl? You can access the root application module from the nested application module by
RootAppModuleImpl root = (RootAppModuleImpl)getRootApplicationModule();If you get a class cast exception it means that there is something wrong with your RooAppModuleImpl. Does it extend ApplicationModuleImpl? If yes the cast should be possible.
Is the root application module of the type RootAppModuleImpl? only then you can access the common methods after getting the root application module.
the next method
private ViewObject getAccountExistsView(DBTransaction t) {
ApplicationModule root = t.getRootApplicationModule();
ViewObject vo = root.findViewObject("MemberExistsView");
if (vo == null) {
vo = root.createViewObject("MemberExistsView","model.MemberExistsView");
return vo;
}doesn't make sense to me. Where does this method reside? in the RootAppModuleImpl? if yes, why do you call getRootApplicationModule? You are in the root application Module. I can' comment on the createViewObject you are calling, but my feeling is that you don't need it either. The view you are creating should be there already if your application module are setup correctly.
And you are right, you should not call createRootApplicationModule if it is not needed. In your case it's not!
Timo