Me too!
In fact, cloudscape must have failed to install even though I tried
the install repeatedly. I am running Win98 (not by choice:-) Tries
the steps in the installed docs buut the cview program doesn't
even run either. Here's the error from cview:
C:\weblogic\eval\cloudscape\lib\unjar>java COM.cloudscape.tools.cview
Exception in thread "main"
***** Error occurred on Tue Mar 27 13:31:18 EST 2001
java.lang.NullPointerException
at com.inprise.jbcl.view.TreeView.setOpaque(TreeView.java:213)
at javax.swing.JScrollPane.<init>(JScrollPane.java:247)
at javax.swing.JScrollPane.<init>(JScrollPane.java:290)
at com.inprise.jbcl.view.TreeView.<init>(TreeView.java:22)
at com.inprise.jbcl.control.TreeControl.<init>(TreeControl.java:22)
at COM.jbms._119._1245.<init>(Unknown Source)
at COM.jbms._119._1245.<init>(Unknown Source)
at COM.jbms._119._1356.<init>(Unknown Source)
at COM.jbms._119._1530.<init>(Unknown Source)
at COM.jbms._119._1530.<init>(Unknown Source)
at COM.cloudscape.tools.cview.main(Unknown Source)
And here's the error from WebLogic:
Tue Mar 27 13:21:14 EST 2001:<I> <WebLogicServer> Invoking main-style
startup weblogic.jdbc.common.internal.JdbcStartup weblogic.jdbc.common.internal.JdbcStartup
Tue Mar 27 13:21:14 EST 2001:<I> <JDBC Pool> Creating connection
pool demoPool with:
{aclName=weblogic.jdbc.connectionPool.demoPool, maxCapacity=2,
initialCapacity=1, url=jdbc:cloudscape:demo, props=user=none;password=none;server=none,
capacityIncrement=1, driver=COM.cloudscape.core.JDBCDriver, poolName=demoPool}
Tue Mar 27 13:21:16 EST 2001:<I> <JDBC Pool> Sleeping in createResource()
Tue Mar 27 13:21:17 EST 2001:<E> <JDBC Pool> Failed to create connection
pool "demoPool"
weblogic.common.ResourceException: weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
DriverManager failed with 'No suitable driver' while trying to
create
a Connection for the 'demoPool' pool. This indicates that the
URL,
jdbc:cloudscape:demo
is not supported by the Driver
COM.cloudscape.core.JDBCDriver
The following is a list of currently loaded JDBC Drivers:
weblogic.jdbc.pool.Driver
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:182)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:109)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:771)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:416)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:330)
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:117)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:125)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:771)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:416)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:330)
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:117)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
Tue Mar 27 13:21:18 EST 2001:<I> <JMS> Beginning startup process
Tue Mar 27 13:21:18 EST 2001:<I> <JMS> Init JMS Security
I guess this is an issue of somebody not controlling where their
binaries are. You can yell "CLASSPATH" and blame it on the user
but so many times (for non-technical users you can do this 0 times.)
Perhaps development shouldn't be done on a Win98 box. How do I
force Cloudscape to install / install its JDBC driver?
Tim
Regards,
Murali