Tuesday, February 5, 2002 11:50 PM
As Tom indicates, this sounds like a classpath issue to me. This is on the order of "is it plugged in and turned on", but in the course I suggest using the extension mechanism as follows:
To avoid classpath issues, copy, and rename where indicated, the following jars from J2EE_HOME/lib/cloudscape to JAVA_HOME/jre/lib/ext:
client.jar rename to cs_client.jar
RmiJdbc.jar rename to cs_RmiJdbc.jar
tools.jar rename to cs_tools.jar
You do not have to rename the jars ( and you can use different names if you like, ) but doing so will avoid any conflicts due to the common names used.
If you have done this *exactly* as instructed and Java still can't find the driver, then the extension mechanism is not working on your platform for some reason. In that case, either add the path to the jars in your CLASSPATH or include the path in your Java invocation.