Deepti Vashisht wrote:I think it is based on the classpath but then i have no control over how the jar files are loaded at runtime by the application server.
Yes, that's a pretty good summary of how it works. Although because Websphere uses a lot of different classloaders, it's a bit more complicated than just "the classpath".
Anyway my suggestion would be to fix your deployment so that you aren't deploying two copies of the resource. Or at least if you must deploy two copies, make sure they contain the same data, so that it doesn't matter which one Websphere chooses.