BUG after deploying/running ADF on 10.1.3(Linux) gives JBO-25002 error

Question

We have found out that there could be a bug in the Linux version of Application Server 10.1.3.0.0 or the Windows version of Jdeveloper.
We are using:
* Application Server 10.1.3.0.0 (Integrated Web Server, J2EE Server and Proces Management) on both a Windows XP machine and a Linux (Red Hat) machine.
* Jdeveloper Version 10.1.3.1.0.3984 (Build JDEVADF_10.1.3.1.0_NT_061009.1404.3984)
We are developing an ADF application using business/ADF components with several jspx pages in the latest version of JDeveloper.
* Testing it on the embedded server of JDeveloper everything works perfectly fine. We can click through all the screens without getting errors;
* After deploying the ADF application to the home instance on the Windows version of 10.1.3 Appplication server everything still works as expected.
* Finally when we deploy the same application to the home instance of the Linux version of the 10.1.3 we are getting the following error after loading the first jspx form page:
500 Internal Server Error
JBO-30003: The application pool (nl.ech.tm.model.service.ECHTMServiceLocal) failed to checkout an application module due to the following exception:oracle.jbo.JboException: JBO-29000: Unexpected exception caught: oracle.jbo.JboException, msg=JBO-29000: Unexpected exception caught: oracle.jbo.NoDefException, msg=JBO-25002: Definition nl.ech.tm.model.dataaccess.TmMarktPartijenRO of type View Definition not found     at oracle.jbo.common.ampool.ApplicationPoolImpl.doCheckout(ApplicationPoolImpl.java:1954)     at oracle.jbo.common.ampool.ApplicationPoolImpl.useApplicationModule(ApplicationPoolImpl.java:2756)     at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:426)     at oracle.jbo.http.HttpSessionCookieImpl.useApplicationModule(HttpSessionCookieImpl.java:258)     at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:397)     at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:392)     at oracle.adf.model.bc4j.DCJboDataControl.rebuildApplicationModule(DCJboDataControl.java:1550)     at oracle.adf.model.bc4j.DCJboDataControl.beginRequest(DCJboDataControl.java:1408)     at oracle.adf.model.binding.DCDataControlReference.getDataControl(DCDataControlReference.java:99)     at oracle.adf.model.BindingContext.get(BindingContext.java:465)     at oracle.adf.model.binding.DCUtil.findSpelObject(DCUtil.java:280)     at oracle.adf.model.binding.DCUtil.findSpelObject(DCUtil.java:248)     at oracle.adf.model.binding.DCUtil.findContextObject(DCUtil.java:383)     at oracle.adf.model.binding.DCIteratorBinding.<init>(DCIteratorBinding.java:127)     at oracle.jbo.uicli.binding.JUIteratorBinding.<init>(JUIteratorBinding.java:60)     at oracle.jbo.uicli.binding.JUIteratorDef.createIterBinding(JUIteratorDef.java:87)     at oracle.jbo.uicli.binding.JUIteratorDef.createIterBinding(JUIteratorDef.java:51)     at oracle.adf.model.binding.DCIteratorBindingDef.createExecutableBinding(DCIteratorBindingDef.java:277)     at oracle.adf.model.binding.DCBindingContainerDef.createExecutables(DCBindingContainerDef.java:296)     at oracle.adf.model.binding.DCBindingContainerDef.createBindingContainer(DCBindingContainerDef.java:425)     at oracle.adf.model.binding.DCBindingContainerReference.createBindingContainer(DCBindingContainerReference.java:54)     at oracle.adf.model.binding.DCBindingContainerReference.getBindingContainer(DCBindingContainerReference.java:44)
We have tried many things:
* Checking the databindings in the model layer of the ADF application
* Checking and testing the datasources on the Linux Application Server
* Using Jdeveloper 10.1.3 and later 10.1.3.1
* Deploy remotely from Jdeveloper
* Deploy the EAR file from the EM consol
* Adding extra ADF/BC4J libraries with the Linux deployment
* Creating another OC4J instance, deploying the BC4J components and redeploying the ADF application
* Reinstalling the Application Server software on Linux (clean install)
Does anyone have a clue why it works on only on Windows and not on Linux?
We have not tried yet :
* To deploy another ADF business components application on the Linux application Server (when I have done this I'll get back to you)
* Compare the versions of the ADF components used on the application server with the versions of the ADF components in the Jdeveloper installation (could there be a difference? Is there a newer version of Application Server 10.1.3 available?).
Cheers,
Thomas

Answer 1

Thank you guys. We have found the solution for the deployment problem on Linux. Oracle technical support has pointed us into the right direction.
During the development process two databindings (XML files) were renamed in the model layer (\Model\classes\model\dataaccess\). Like for example we had a data binding called DTBinding.xml that was renamed to DtBinding.xml. The changes were applied in the source code of the project. After depoyment to the application server it seems that the old databinding file was still there (DTBinding.xml). This was the cause of the JBO-25002 error on Linux. After renaming DTBinding.xml to correct file name DtBinding.xml (in the folder /opt/oracle/product/10.1.3.1/OracleAS_1/j2ee/OC4J_TMFB/applications/APPNAME/APPNAME/WEB-INF/classes/model/dataaccess) and restarting the OC4J instance on the application server the application was finally working on Linux.
A few things to keep in mind when you are developing on Windows and deploying to Linux:
* The Windows OS is not looking at uppercase characters in XML file names. As long as the file name of the XML is correct it will be found.
* It seems that changes in the databinding filenames in the JDeveloper (10.1.3.1) source code are not correctly submitted after building and deploying the project. So be carefull with changing names.
Cheers,
Thomas