Works in Enterprise Manager version of 10g but not standalone (OC4J)

Question

ok.... on one box I'm running 10g Enterprise Manager version of the app server (v9.0.4) and on another box I'm running the standalone version of the app server (OC4J v9.0.4). I have an ear file that works in the EM version, but won't work in the OC4J version. (the ear worked in both app servers until recently when we added some code using classes in jakarta-poi-2.0-pre3.jar..... added this jar file to the WEB-INF/classes folder of the ear file; the orion-application.xml file library path points to this folder for its library (because some of our classes on the EJB side of things use the classes in the jar file) so in theory the jar file should be found by the application (and there are other jar files in there that ARE being found on both versions....)). So.... any ideas why the standalone version (OC4J) would be having problems? Could it be that a different classloader setup is used in OC4J?
Scott

Answer 1

well, I found the problem.... the orion-application.xml file in the C:\OC4J\j2ee\home\application-deployments\[appname] folder was not being updated with the new version upon redployment.... don't know why that wasn't happening. I'm using hot deploy and redeploying the application by copying the ear file to the C:\OC4J\j2ee\home\applications folder. Shouldn't this cause a refresh of the files in the application-deployment folder too?? In any case, I manually edited the orion-application.xml file in the application-deployments folder to reflect the new library conditions and it works..... Additional info: i just redeployed the app again, and the timestamp on the .../application-deployments/orion-application.xml file was updated, so it appears that it is being updated but apparently from a cached version that does not reflect the new version of the orion-application.xml file in the new ear being deployed.... strange and sad.