An ear file is extracted and the files are placed uncompressed on the file system. But that's more temporary storage than a cache.
Are you having a ClassNotFoundException or something of the sort? Changes not being incorporated after deployment?
Joined: Jun 26, 2001
Hi Cameron McKenzie,
Thanks for your reply.
Our Websphere app server has recently been upgraded to version 184.108.40.206 on both Dev and QA. One of our apps on DEV failed after the upgrade -- I should say the app was ok initially after the server upgrade and the problem only occurred after we edited an simply jsp page and redeployed the app to the DEV server. We found that an older version of a jar file causes the problem in upgraded server environment and problem resolved after we replace the jar file with a new one.
So after QA server was upgraded to the version 220.127.116.11, I expected that app on QA to fail because of that jar file. But it didn't fail. I have the same package (old jar file in it) redeployed to QA server and the app still worked. I am a bit puzzled by that. That is why I am wondering if cache may play a part in this?
Thanks a lot,
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Does Webshpere App Server 6.1 cache jar files?