Hi,
I resolved the question below. It is a bit of a gotcha for inexperienced
users of Turbine. When you switch database type for your application just
running 'ant init' from your project build directory is not enough. It
occurred to me that the original 'ant' run from the tdk directory may have
produced files specific to the Turbine security tables. So I ran it again
with Oracle specified as the database.
Here are the things to look out for.
1. If you have developed your schema beyond the original creation then the
ant task will clobber the up-to-date one in your application conf directory
with the one you originally created to start your application off.
2. Your TurbineResources.properties file will be overwritten.
Just as well I zipped the whole thing before trying this out!
The problem I have now is that while the Turbine application runs the first
attempt to access the database causes an exception
[Thu Nov 22 14:19:42 GMT+00: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.
[Thu Nov 22 14:19:42 GMT+00:00 2001] -- ERROR --
Exception: org.apache.turbine.services.InitializationException:
TurbineSchedulerService failed to initialize: 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)
This is confusing because I have the required properties and TNS Listener is
running and the Trubine_* tables exist and are populated where required.
Here are the entries in TurbineResources.properties. Oracle's JDBC driver
jar 'classes_12.zip' is in the classpath and in the lib directory.
database.default.driver=oracle.jdbc.driver.OracleDriver
database.default.url=jdbc:oracle:thin:@localhost:1521:roamware
database.default.username=David
database.default.password=blahhh
database.adaptor=DBOracle
database.adaptor.DBOracle=oracle.jdbc.driver.OracleDriver
What am I missing? Also I assume that the "Orable 8i Howto" is out of date
as I cannot find any oracle*.sql files referred to there?
thanks
David
-----Original Message-----
From: David Wynter [mailto:[EMAIL PROTECTED]]
Sent: 21 November 2001 14:14
To: Turbine-User
Subject: TurbineSchedulerService.init error using Oracle 8i
Hello,
I have built an application using TDK 2.1 on W2K using JRE 1.2.2 on MySQL.
It works. I have just tried the same on Oracle 8.1.5 on the same OS. I had a
previous post to the list where I was informed to use the updated db.props
for Oracle. This I did. At the time I just needed the project specific SQL
for review and it worked fine for that. Now that I need to run the
application I discovered that it complained about all tables that had the
RAW data type. The db.props had the following:
BINARY = RAW
VARBINARY = RAW
I found that RAW must have a size defined so I changed the lines to:
BINARY = RAW (2000)
VARBINARY = RAW (2000)
It now builds successfully.
However when I point the browser at the application I get a NPE, top part of
the stack trace follows:
java.lang.ExceptionInInitializerError: java.lang.NullPointerException
at org.apache.turbine.services.schedule.JobEntryPeer.(JobEntryPeer.java)
at
org.apache.turbine.services.schedule.TurbineSchedulerService.init(TurbineSch
edulerService.java:121)
at
org.apache.turbine.services.TurbineBaseService.init(TurbineBaseService.java:
108)
at
org.apache.turbine.services.BaseInitableBroker.initClass(BaseInitableBroker.
java, Compiled Code)
at
org.apache.turbine.services.BaseServiceBroker.doInitService(BaseServiceBroke
r.java:226)
at
org.apache.turbine.services.BaseServiceBroker.initServices(BaseServiceBroker
.java, Compiled Code)
at org.apache.turbine.Turbine.init(Turbine.java:185)
The Turbine_Scheduled_Job table exists and has no rows in it.
Ive looked through the archives and can find nothing on this problem. Any
ideas anyone?
Regards
David
--
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]>
