Fixed it.
It seems that some how the default database name in Turbine.properties did
not match with what was hard coded into the the Torque generated om maps
within the doBuild() method of my map builder is this line:
dbMap = TurbineDB.getDatabaseMap("jstore");
Well, my turbine.properties looked like this:
services.PoolBrokerService.defaultPool = store
services.MapBrokerService.defaultMap = store
As soon as I changed them to this:
services.PoolBrokerService.defaultPool = jstore
services.MapBrokerService.defaultMap = jstore
and restarted tomcat, everything worked fine.
Scott
-----Original Message-----
From: Weaver, Scott [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 12, 2001 5:01 PM
To: Turbine Users List
Subject: Peer doSelect() failing with a null connection object.
My om Peers are throwing exception do to the fact that the connection object
they are using is null.
Error Screen:
"org.apache.turbine.util.TurbineException: Error rendering Velocity
template: screens/ToolTest.vm: Error rendering Velocity template:
screens/ToolTest.vm: Invocation of method 'getStores' in class
com.rippe.essential.store.tools.StoreTool threw exception class
java.sql.SQLException : Connection object is null! "
getStores() is actually invoking StorePeer.doSelect(new Criteria()), which
is having trouble getting a hold of a connection object.
I am able to sign into the Turbine login screen and add users and what not
but when I try to use any of my Torque generated peers, I always get a null
connection object exception. Any ideas???
Thanks,
Scott
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
