The getting started is a bit of a mess. I got them partially done at a
time when the guys who really know were too busy to work on it and now I
am up to me ears in work and Christmas.
I will try to take some time during the last week of the month to see if
I can get the documentation to a state where it makes some sense again.
Sorry for the confusion that the current incomplete state is causing.
Ron
Joachim Müller wrote:
Hi Ron.
According to the documentation the driver.path variable is emty on default.
It might be better to state that this property should point to the drivers
location.
The getting startet with source guide is outdated(?), because derby is used as
default database now instead of hsql.
Joachim
Ron Wheeler wrote:
You need to fill in the org.apache.jetspeed.test.jdbc.drivers.path with
the path to the driver.
The error message says that it can not fine the driver. With no path it
is probably looking for the org.hsqldb.jdbcDriver on the root ( / )
directory which is not likely where you have put it. Find
org.hsqldb.jdbcDriver and then tell Jetspeed where it is.
Partridge, Terry A wrote:
I am having a similar problem using the HSQL database. I followed the
getting started instructions for building and deploying Jetspeed2. I
encounter no problems during the build and deployment steps. When I
attempt to access http://localhost:8080/jetspeed, I get a number of
error messages relating to the database. When I look at the
jetspeed.log in the jetspeed webapp, I see this error statement
"Cannot load JDBC driver class 'org.hsqldb.jdbcDriver". Apparently I
am missing some configuration parameter, I assume.
My build.properties for the database are as follows:
org.apache.jetspeed.test.database.url = jdbc:hsqldb:hsql://127.0.0.1:9001
org.apache.jetspeed.test.database.driver = org.hsqldb.jdbcDriver
org.apache.jetspeed.test.database.user = sa
org.apache.jetspeed.test.database.password =
org.apache.jetspeed.test.jdbc.drivers.path=
org.apache.jetspeed.test.database.default.name=hsql
org.apache.jetspeed.production.database.url =
jdbc:hsqldb:hsql://127.0.0.1:9001
org.apache.jetspeed.production.database.driver = org.hsqldb.jdbcDriver
org.apache.jetspeed.production.database.user = sa
org.apache.jetspeed.production.database.password =
org.apache.jetspeed.production.jdbc.drivers.path=
org.apache.jetspeed.production.database.default.name=hsql
Regards, Terry
-----Original Message-----
From: Ron Wheeler [mailto:[EMAIL PROTECTED] Sent:
Tuesday, December 13, 2005 5:51 AM
To: Jetspeed Users List
Subject: Re: database settings problem
You might want to post your build file and tell us what error message
you are getting.
Ron
Joachim Müller wrote:
Hi all.
With the 2.0 released sources we encounter the following problem:
1.) If we ommit the database settings from build.properties the build
process generates SQL files for derby but HSQL will be used as
default database.
2.) If we define HSQL as database in the build.properties tomcat
failes to start jetspeed with an exception.
Can somebody confirm this?
Joachim
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
