Re: Detecting multiple class loaders

Chris wrote:

No, it's actually only one webapp. It's a data file. Using a database is not an option. The only approach is to access the file through only one synchronized class.

I think you may have already decided on which approach is best, but I'm still somewhat confused. I don't know everything, so it helps me out sometimes if I ask questions.

You have one web app, which is implemented as multiple "web apps" on Websphere? So conceptually you have one app, but Websphere sees multiple apps?

I'm asking because I assume I may run into the same problem at some point in my career, and I'd like to know about problems before I hit them, at least, if not also have some idea what a solution might be....

The only other reason for multiple classloaders that I can think of is if there's multiple JVMs, on one or multiple machines.

It sounds like you need some sort of global or JVM wide context object, where you can store one class object that all web apps can use. I've never heard of such a thing though.
.

Relevant Pages