Discussion:
EJB Recompilation
(too old to reply)
cabuki
2006-02-23 09:44:51 UTC
Permalink
I've recently switched from Windows to Mac. My company uses Ant for our
builds and they are deployed to a WebLogic 8.1 installation. The build
runs correctly and everything gets pushed to the server just fine. When
I try to start my appserver, WebLogic tries to recompile the EJBs.
During the build, we use weblogic.appc to compile the EJBs.

<java classname="weblogic.appc"
classpath="${wl.classpath};${external.classpath}"
fork="true"
failonerror="true">
<arg line="-compiler javac -J-mx192m ${keepGenerated} -deprecation
-O -output
${build.out}/${releng.project}-toolbox-ejb.${build.devtrigram}.jar
${build.out}/${releng.project}-toolbox.${build.devtrigram}.jar"/>
</java>
From searching the internet, it seems this happens when the version to
compile the EJBs is different than the one used on the server. However,
that isn't the case. I have WebLogic 8.1 sp3 installed on my Mac:

$ java -cp ~/src/weblogic/813/weblogic81/server/lib/weblogic.jar
weblogic.version

WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973

and on the server:

$java -cp /weblogic/weblogic81/server/lib/weblogic.jar weblogic.version

WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973

I'm 100% sure they are on the classpath. I've had no luck tracking down
why it's doing this. Can anyone help me?
cabuki
2006-02-23 10:17:35 UTC
Permalink
I found the culprit. Previously, I had deployed a version compiled
against SP5 as a test. That version was cached in my staging area. I
cleared out the staging area and it works correctly now.

Loading...