Classpath Problem in WebSphere 6.0 (WAS 6.0)

Question

We were trying to configure WAS 6 for the last 10 days to work for an existing application.
The problem was pointing to some jar files (log4j, j2sh and jdom etc). Although we added it to the class path of the EJB project but still RAD was not picking it up at run time. Following 2 steps helped us solve it
1. For referring to any jar file that RAD is not picking up, add that jar directly to your EAR project (copy it rt in the EAR Project) and make your EJB and WAR projects point to it though JAVA JAR DEPENDENCIES tab from the project properties. Since this was the first time we were working with RAD, we wasted a lot of time trying to figure this workaround.
2. If there is any jar file (like jdom) that is already present in the lib directory of your Server, then the CLASSLOADER will refer to that version, not the version that we configure using CLASSPATH of our EJB Project. Thus, replace the older version of all the jar files in the lib directory of server with the latest version that you want it to work with.
All this might be pretty much obvious to experts but being a novice and having spent a lot of time, I thought that this may help someone out there.

Answer 1

We were trying to configure WAS 6 for the last 10 days to work for an existing application.
The problem was pointing to some jar files (log4j, j2sh and jdom etc). Although we added it to the class path of the EJB project but still RAD was not picking it up at run time. Following 2 steps helped us solve it
1. For referring to any jar file that RAD is not picking up, add that jar directly to your EAR project (copy it rt in the EAR Project) and make your EJB and WAR projects point to it though JAVA JAR DEPENDENCIES tab from the project properties. Since this was the first time we were working with RAD, we wasted a lot of time trying to figure this workaround.
2. If there is any jar file (like jdom) that is already present in the lib directory of your Server, then the CLASSLOADER will refer to that version, not the version that we configure using CLASSPATH of our EJB Project. Thus, replace the older version of all the jar files in the lib directory of server with the latest version that you want it to work with.
All this might be pretty much obvious to experts but being a novice and having spent a lot of time, I thought that this may help someone out there.