DEPLOY PROBLEM URGENT

Question

Hi,
using JDeveloper 10.1.3.3 ADF BC & JSF. Until today we have deployed all our applications to: Standalone Oracle Enterprise Manager 10g Application Server Control 10.1.3.1.0 throught JDeveloper, I would right click on web.xml, create War deployment profile... and then right click test.deploy and Deploy to AppServer, and everything worked fine.
But today we tried to move to:
Oracle Enterprise Manager 10g Application Server Control 10.1.2.0.2
Supported Target Application Servers 10.1.2.0.2
and we cannot deploy any of our applications through JDeveloper, so we tried to do it manually through OC4J Home -> Applications -> Deploy WAR file... browsed and selected test.war entered Application Name and Map to URL... and got following error:
Failed to deploy web application "Test". Failed to deploy web application "Test". . Nested exception
Resolution:
Base Exception:
java.rmi.RemoteException
deploy failed!: ; nested exception is:
oracle.oc4j.admin.internal.DeployerException: Unknown assembly root-tag attribute: xmlns:xsi. deploy failed!: ; nested exception is:
oracle.oc4j.admin.internal.DeployerException: Unknown assembly root-tag attribute: xmlns:xsi
I've googled a bit and found that I should change following tag in web.xml
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
version="2.4"
xmlns="http://java.sun.com/xml/ns/j2ee">
with
<!DOCTYPE web-app PUBLIC
"-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
since I've read:
"To be more precise, deployment descriptors which refer to XML Schema definitions are
only used in J2EE 1.4 and later, but not in J2EE 1.3 or earlier.
OC4J 9.0.4.x and 10.1.2.x support J2EE 1.3 while OC4J 10.1.3 supports J2EE 1.4."
Changing that tag underlines following in web.xml and says Element dispatcher not expected, but I can compile and run application without problems:
<filter-mapping>
<filter-name>adfFaces</filter-name>
<servlet-name>Faces Servlet</servlet-name>
<dispatcher>FORWARD</dispatcher>
<dispatcher>REQUEST</dispatcher>
</filter-mapping>
So I've, rebuilded and created .war and .ear files, and tried to deploy again, but this time I've got the following error:
Failed to deploy web application "Test". Failed to deploy web application "Test". . The evaluate phase failed. The Adapter used in the evaluate may have thrown an exception.
Resolution:
Please call Oracle support.
Base Exception:
java.lang.NoClassDefFoundError
oracle/adf/share/logging/ADFLogger. oracle/adf/share/logging/ADFLogger
I don't know what changes need to be done in my applications (which files to modify) to be able to deploy to Oracle Enterprise Manager 10g Application Server Control 10.1.2.0.2, if anyone has any suggestion or knows what should be done please help, this is quite urgent & important since we plan to migrate all of our applications to this new application server.
Thanks in advance,
Tomislav.

Answer 1

No success at all.
So far what I gathered from the link you posted and tried:
Note:
"J2SE 1.4.2 is in its Java Technology End of Life (EOL) transition period. The EOL transition period began Dec, 11 2006 and will complete October 30th, 2008, when J2SE 1.4.2 will have reached its End of Service Life (EOSL). Customers interested in learning more about Sun's Java Technology Support and EOL policy"
I cannot find the version 1.4.0. so I've downloaded j2sdk1.4.0_04 and installed it.
To configure JDeveloper to build projects with JDK 1.4:
1.Install J2SE 1.4 on the machine running JDeveloper.
2.Configure JDeveloper with the J2SE 1.4 that you installed:
a.In JDeveloper, choose Tools > Manage Libraries. This displays the Manage Libraries dialog.
b.In the Manage Libraries dialog, choose the J2SE Definitions tab.
c.On the right-hand side, click the Browse button for the J2SE Executable field and navigate to the J2SE_1.4/bin/java.exe file, where J2SE_1.4 refers to the directory where you installed J2SE 1.4.
d.Click OK.
3.Configure your project to use J2SE 1.4:
a.In the Project Properties dialog for your project, select Libraries on the left-hand side.
b.On the right-hand side, click the Change button for the J2SE Version field. This displays the Edit J2SE Definition dialog.
c.In the Edit J2SE Definition dialog, on the left-hand side, select 1.4 under User.
4.Click OK in the Edit J2SE Definition dialog.
5.Click OK in the Project Properties dialog.
did that.
When you run an Oracle JDeveloper 10.1.3 application using the Embedded OC4J server, the application is configured for JDK 1.5. If you then try to switch to JDK 1.4, you will see JSP compile failures. To remedy this you need to force the application files to be re-compiled when OC4J is restarted with JDK 1.4. To configure Embedded OC4J to JDK 1.4:
1.Configure JDeveloper 10.1.3.4 according to the steps above.
2.Stop the embedded OC4J server instance.
3.Delete the following directory:
ORACLE_HOME/j2ee/instance/application-deployments ( I guess this is the following directory: C:\JDeveloper\jdev\system\oracle.j2ee.10.1.3.41.57\embedded-oc4j\application-deployments)
4.Start the embedded server again.
did that.
After doing the steps mentioned above I've created new test app with just one page and tried to run, got following error:
OC4J startup failed
org.xml.sax.SAXException: META-INF/boot.xml in C:\JDeveloper\j2ee\home\oc4j.jar, line 241: Shared loader 'oc4j.internal' cannot be found.
     at oracle.classloader.util.XMLConfiguration.fail(XMLConfiguration.java:1279)
     at oracle.classloader.util.XMLConfiguration.addImport(XMLConfiguration.java:1253)
     at oracle.classloader.util.XMLConfiguration.startElement(XMLConfiguration.java:630)
     at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1535)
     at org.apache.crimson.parser.Parser2.content(Parser2.java:1824)
     at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1552)
     at org.apache.crimson.parser.Parser2.content(Parser2.java:1824)
     at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1552)
     at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:534)
     at org.apache.crimson.parser.Parser2.parse(Parser2.java:318)
     at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)
     at oracle.classloader.util.XMLConfiguration.configureLoaders(XMLConfiguration.java:277)
     at oracle.oc4j.loader.boot.XMLPlusClassPathBootConfiguration.configureLoaders(XMLPlusClassPathBootConfiguration.java:84)
     at oracle.classloader.util.InitialLoadersFactory.populateLoaders(InitialLoadersFactory.java:389)
     at oracle.classloader.util.InitialLoadersFactory.initLoaders(InitialLoadersFactory.java:230)
     at oracle.classloader.util.InitialLoadersFactory.create(InitialLoadersFactory.java:167)
     at oracle.oc4j.loader.boot.BootStrap.main(BootStrap.java:26)
Process exited with exit code 0.
Also what do you mean by
Did you install the ADF Runtime libraries from 10.1.3 on the OAS 10.1.2?
In the document you linked to, it says:
Before you can deploy applications that use ADF on third-party application servers, you need to install the ADF runtime libraries on those application servers. You can perform the installation using a wizard or you can do it manually:
*For WebLogic, JBoss, and Tomcat, you can install the ADF runtime libraries from JDeveloper using the ADF Runtime Installer wizard. See Section 34.12.1, "Installing the ADF Runtime Libraries from JDeveloper".
*For WebSphere, you have to install the ADF runtime libraries manually. See Section 34.12.2, "Configuring WebSphere 6.0.1 to Run ADF Applications".
*For all application servers, you can install the ADF runtime libraries manually. See Section 34.12.3, "Installing the ADF Runtime Libraries Manually".
but we're not using third party app servers since this is not standalone version, we used tomcat before, now colleague that installed OAS told me it doesn't use third party app servers.
What do you mean by this:
"If you did try including the ADF logger library in your deployment file."
How do I do that?
So now I cannot run embbed app server and test locally using j2sdk1.4.0_04 no matter what I try, and still no luck with deploy. I'm afraid that if I cannot do this with newly created test apps without any complexity, what kind of problems will I have to deal with real production apps...
I'll keep trying and I'll post if I figure out anything,
suggestions and help is more than aprechiated,
thanks in advance,
Tomislav.