ADF application deployed to Weblogic producing runtime error

Question

Hi all,
We are trying to deploy a new ADF application built by JDeveloper 11.1.1.5.0 to a standalone weblogic (*version 10.3.1.0*)
The app deploys and runs on integrated wls without any problems, and deploys to the standalone wls without any warnings or errors, but does not run on standalone wls :(
I checked many possible errors and tried many possible solutions, including, but not limited to;
--> Checked tag references and page components on jsp/jspx pages, deleted unused or possibly unsupported tags from pages and taglibs from ui project (trinidad components 1.2), but still I get the error
--> Using 2 different machines with JDev 11.1.1.5 we created test applications with same tech stack, tag libraries and tag references, deployed to standalone wls and they run without problems (!)
--> Checked web.xml, the file contents and references are the same as of other applications whic are deployed from same environment to the same standalone wls and running without problems (these applications are referenced as "other working applications" following this line)
--> In sessions.xml, the db connection is default, the file includes 2 references <server-platform xsi:type="weblogic-10-platform"/> and <primary-project xsi:type="xml">META-INF/tlMap.xml</primary-project>
--> All projects (Model and view) are cleaned and rebuilt, deployment files are recreated, application ear is recreated, runtime application name and context root name ise changed, but still no luck, I get the same error
--> Project technology stacks are checked and all tech stacks are configured same as "other working apllications" (since their technical architectures are the same)
--> Checked application datasources; database connections of this application automatically create datasources, for connection dbconn1 there exists a datasource named dbconn1DS as a module in the deployed application. Other working applications had datasources with same name; to prevent a possible conflict in JNDI names of these datasources I changed the name of the db connection to a unique name, deleted the old connection and datasource. But still no luck, error is still SAME.
--> Test applications (which have trinidad components 1.2 as tag library and there are references to it from page files) run on standalone wls, removing this taglib and the references does not make a difference. But the real application gives error when trinidad is removed from the tag libraries (java.lang.NoSuchMethodError: resetADFContext)
--> Created new jspx pages which are not using backing beans and tried to access these, but I received the SAME error for these pages as well. Removed all jspx pages except the dummy test pages, and still no change.
One final note; html pages in the project open without problems, as their url are different from the jspx files ( "host/appName/Test.html instead" of "host/appName/faces/Test.jspx" ) and when these pages open, the server log and console indicates new sessions created by this request.
This is the famous error I get on the server log every time I try to access a jspx file:
####<Jul 31, 2012 9:14:12 AM EEST> <Error> <HTTP> <hostname> <ADF_SRV1> <[ACTIVE] ExecuteThread: '24' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1343715252920> <BEA-101020>
<[ServletContext@142296767[app:KiymetliEvrak module:KiymetliEvrak path:/KiymetliEvrak spec-version:2.5]] Servlet failed with Exception
java.lang.NullPointerException
     at oracle.adfinternal.controller.util.AdfvInterfaceImpl.addQueryParameters(AdfvInterfaceImpl.java:162)
     at oracle.adfinternal.controller.state.ControllerState.initializeUrl(ControllerState.java:708)
     at oracle.adfinternal.controller.state.ControllerState.synchronizeStatePart2(ControllerState.java:467)
     at oracle.adfinternal.controller.application.SyncNavigationStateListener.afterPhase(SyncNavigationStateListener.java:46)
     at oracle.adfinternal.controller.lifecycle.ADFLifecycleImpl$PagePhaseListenerWrapper.afterPhase(ADFLifecycleImpl.java:531)
     at oracle.adfinternal.controller.lifecycle.LifecycleImpl.internalDispatchAfterEvent(LifecycleImpl.java:120)
     at oracle.adfinternal.controller.lifecycle.LifecycleImpl.dispatchAfterPagePhaseEvent(LifecycleImpl.java:168)
     at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener$PhaseInvokerImpl.dispatchAfterPagePhaseEvent(ADFPhaseListener.java:124)
     at oracle.adfinternal.controller.faces.lifecycle.ADFPhaseListener.afterPhase(ADFPhaseListener.java:70)
     at oracle.adfinternal.controller.faces.lifecycle.ADFLifecyclePhaseListener.afterPhase(ADFLifecyclePhaseListener.java:53)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:352)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:165)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:85)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:421)
     at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:54)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:421)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
     at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at oracle.security.jps.wls.JpsWlsFilter$1.run(JpsWlsFilter.java:96)
     at oracle.security.jps.wls.JpsWlsFilter.doFilter(JpsWlsFilter.java:140)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:202)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3588)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
Could anybody please help, where to focus to see the REAL indications and solutions of this annoying error? Soon I will get this application to production environment, so any help would be appreciated.
Thanks in advance...

Answer 1

Ok, I think I should give the update, on how I struggled to solve the problem;
--> I did NOT update the wls, since it is the production server and has many applications and services running on it , I could not take the risk of breaking those.
--> I migrated, or rewrote the application on JDeveloper 11.1.1.1.0, rewrote the toplink map file, descriptors, pageDefs bla bla, to make it compatible with wls 10.3.1.0.
--> Then I tested the app on JDev 11.1.1.1.0 ok, then opened the same application on JDev 11.1.1.5.0 then tested ok....
--> And I deployed the application from JDev 11.1.1.5.0 to the standalone wls, and this is where the magic happened, the app worked without error on standalone wls 10.3.1.0
+( Just a note: I really wonder, where is the backward, or forward compatibility of ide and server runtimes? )+
Anyway, it is a big lesson for me about choosing the ide version for a specific server.
Thank you...