EJB recompile during deployment

Question

Hi,
What are the criteria for the WebLogic Server (we use 9.1) for recompiling
EJBs? I have build an Application with several EJB.jar files in a directoy
structure that is something like this:
Application
|- deploy
| |- foo-EJB.jar
| |- bar-EJB.jar
|- libraries
| |- commons-lang-2.1.jar
|- META-INF
| |- MANIFEST.MF
| |- application.xml
| |- weblogic-application.xml
|- other-stuff
When I deploy this application directly from this directory on a Windows PC,
erverything works fine, but after packing it into an ear file, putting it
on a SUN machine and deploying the ear file, the server starts recompiling
several of the EJB.jar files. Why is it doing this?
Greetings,
Chris

Answer 1

Olav,
<load-on-startup> in web.xml will work only when you have load-on-startup="true" in your http-web-site.xml for your web module.
for example <web-app application="work" name="work" root="/work" load-on-startup="true"/>
This is documented in http://otn.oracle.com/tech/java/oc4j/htdocs/OC4J-WEB-FAQ.html#1
regards
Debu
Hi!
Currently I am working on an application that we are deploying on the oc4j-server and simultaneously on the SUN reference-implementation. Using the deployment descriptor I define the order of instantiation of the servlets (<load-on-startup>). This works fine using the SUN server. Deploying the application on the oc4j-server does not get to the servlet-initialization since the server tries to create the EJBs first. I would gladly tell the server somehow that this is both not necessary and even rather problematic to the application. Does anybody know how to achive this?
Thanks in advance!
Cheers,
Olav