An EJB was developed using WSAD 4.0, and is deployed on WAS 4.0. I'm trying to use those EJB interface components from within my WSAD 5.0 and WAS 5.0. I'm getting lots of 'ClassNotFound' exceptions, which indicates that there are issues with the jar files referenced. While I've been able to resolve these problems by putting the various jar files that contain the missing class files into my class path, this seems like quite a kludge - we're hunting around, searching through the masses of jar files in WSAD looking for the right jar files - the classes appear to be found in multiple jar files. My question is this: this CAN'T BE a unique problem. There has to be some coherent method that enables us to do this withouth this hunt & peck method. Worse yet would be the scenerio where I develope and host the EJB under WSAD and WAS 5.0, and my client EJB user is on WSAD and WAS 4.0!!! How is THAT supposed to work - they won't even have the jar files at their disposall! This appears to me to make EJBs an almost unworkable technology - at least as implemented within the WSAD and WAS envirionment. Help! Am I missing something, or is this really as bad as it seems?