I use Turbine with oracle (the same version) and have no problem.
Everything you've done is ok except for touching things under TDKROOT/share.
You have to make the changes in APPNAME/WEB-INF/conf/TurbineResources.properties
BTW, I also renamed the jdbc driver from .zip to .jar.
Gabriel
Pfitzenmaier Philipp wrote:
> Hi,
>
> after reading the docs and the mail archive on my problem I still can't get
> the demo application to work with my Oracle 8i (8.1.7) after several days
> (shame on me).
>
> problem: I even can't do the login - instead of the "welcome" page I always
> get an error. The relevant part of the log is included below - it seems to
> me that turbine can't find my driver.
>
> What I did so far is:
> - unziped the tdk archive
> - left build.properties in TDK root unmodified, so app.name = newapp
> - ran ant on TDK root
> - modified build.properties in "/TDKROOT/webapps/APPNAME/WEB-INF/build" and
> set all oracle properties:
>
> database=oracle
> database.manual.creation = true
>
> databaseUrl = jdbc:oracle:thin:@hostname:1521:dbname
> databaseDriver = oracle.jdbc.driver.OracleDriver
> databaseUser = myORALogin
> databasePassword = myORAPassword
> databaseHost = hostnameOfMyOracleServer
>
> - copied oracle drivers to "/TDKROOT/webapps/APPNAME/WEB-INF/lib"
> - modified "/TDKROOT/share/conf/TurbineResources.properties"
>
> database.adaptor=DBOracle
> database.adaptor.DBOracle=oracle.jdbc.driver.OracleDriver
>
> database.default.driver=oracle.jdbc.driver.OracleDriver
> database.default.url=jdbc:oracle:thin:@tr030022:1521:VDEV
> database.default.username=myORALogin
> database.default.password=myORAPassword
>
> and set and "/TDKROOT/share/conf/database/oracle" to my db data as well
>
> - ran ant init in "/TDKROOT/webapps/APPNAME/WEB-INF/build"
>
> The sql scripts are executed at this point! So the oracle driver seems to be
> present and working...
>
> - started catalina
> - browsed to homepage with login screen and tried to login "turbine/turbine"
>
> Here is the extract from the turbine.log:
>
> <snip>...
> [Fri Jun 22 16:17:00 GMT+02:00 2001] -- INFO -- IDBroker thread was started.
> [Fri Jun 22 16:17:00 GMT+02:00 2001] -- INFO -- Start Initializing service
> (late): PoolBrokerService
> [Fri Jun 22 16:17:00 GMT+02:00 2001] -- INFO -- Finish Initializing service
> (late): PoolBrokerService
> [Fri Jun 22 16:17:00 GMT+02:00 2001] -- WARN -- IDBroker is being used with
> db: default
> which does not support transactions. It is possible to
> generate duplicate keys, if multiple JVM's are used or other
> means are used to write to the database.
> [Fri Jun 22 16:17:00 GMT+02:00 2001] -- ERROR --
> Exception: java.sql.SQLException: No suitable driver
> Stack Trace follows:
> java.sql.SQLException: No suitable driver
> at java.sql.DriverManager.getConnection(DriverManager.java:537)
> at java.sql.DriverManager.getConnection(DriverManager.java:177)
> at org.apache.turbine.util.db.adapter.DB.getConnection(DB.java:153)
> at
> org.apache.turbine.util.db.pool.ConnectionPool.getNewConnection(ConnectionPo
> ol.java:498)
> at
> org.apache.turbine.util.db.pool.ConnectionPool.getConnection(ConnectionPool.
> java:339)
> at
> org.apache.turbine.services.db.TurbinePoolBrokerService.getConnection(Turbin
> ePoolBrokerService.java:171)
> at
> org.apache.turbine.services.db.TurbinePoolBrokerService.getConnection(Turbin
> ePoolBrokerService.java:145)
> at
> org.apache.turbine.services.db.TurbineDB.getConnection(TurbineDB.java:169)
> at
> org.apache.turbine.om.peer.BasePeer.initTableSchema(BasePeer.java:217)
> at
> org.apache.turbine.om.peer.BasePeer.initTableSchema(BasePeer.java:194)
> at
> org.apache.turbine.om.security.peer.TurbineUserPeer.<clinit>(TurbineUserPeer
> .java)
> at
> org.apache.turbine.services.security.db.DBUserManager.retrieve(DBUserManager
> .java:158)
> at
> org.apache.turbine.services.security.db.DBUserManager.retrieve(DBUserManager
> .java:246)
> </snip>....
>
> I'm pretty much clueless right now. The driver seems to work (I can connect
> with these setting from an application without any problems), as the tables
> are created and populated as well. But why doens't it work in the demo app?
> As you can guess, any help or clue is highly appriciated ;-)
>
> Thanks for your time and help,
>
> Philipp
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
