Progress - Sort Of
Found some more information on configuring JDeveloper 10.1.3 to build applications that can run on OAS 10.1.2. I had to install the JDev 10.1.3 ADF runtime library on the OAS (instructions in Section 22-12 of the Oracle® Application Development Framework Developer's Guide (10.1.3). Then I found additional steps for creating deployment files in section 34.6.2 of the Oracle® Application Development Framework Developer's Guide For Forms/4GL Developers Guide. I was still unable to deploy from JDev, so I copied the .EAR file to the OAS, and tried deploying with Enterprise Manager. Success! But now I'm getting a "500 Internal Server Error". I believe this is yet another J2EE/JDK version issue. (JDev uses J2EE 5 and JDK 1.5, OAS 10.1.2. uses an older version). At least the application is deployed and shows a loaded status and I'm not getting 404 Page Not Found errors when I try to run it from the browser.
The 500 Internal Server Error's stack dump shows it's related to ADF - maybe I can make a simple JSP without ADF and get it to run. I only need JDev so I can build a very simple page anyways.
Update: Success! I copied a one-line example of a JSP into a new JDev web applications project, followed the steps to package it for OAS 10.1.2, deployed it from JDev, and IT WORKED.
It's Friday afternoon - I'm going sailing and them I'm going to drink some beer, and then I'm going to repeat that process Saturday and Sunday. Nice weekend all!
Labels: ADF, JDeveloper, JSP, OAS
1 Comments:
To put it mildly, I'm struggling through getting a JDeveloper 10.1.3 application deployed and running on OAS 10.1.2.
I've managed to make some changes to get the ear file deployed, but the application's status is indicating "Not Loaded".
I can not get the deployed application to launch, and I am assuming it may in part be due to the status of Not Loaded.
What do I need to do have the application's status to be "loaded"?
Post a Comment
Subscribe to Post Comments [Atom]
<< Home