[daisy] Installing Daisy 1.2pre3 on PostgreSQL 7.1.3?

[Olivier Lange]

Hello all!

To successfully deploy Daisy I would need to install Daisy on Solaris 
with PostgreSQL 7.1.3. This is still the same project I evaluated and 
skinned Daisy 1.1 earlier last year.

For now, I am trying to install Daisy under Debian Linux kernel 2.4.18 
with PSQL 7.1.3, Java2 SDK 1.4.2_07, Ant 1.6.2.

I ran into trouble as soon as I tried to setup the OPENJMS repository 
database.

Before any specifics: do you think Daisy could run on PSQL 7.1.3? I saw 
it would run on PSQL in the Daisy 1.2pre3 upgrade notes, but is there a 
minumum version requirement?

The JDBC drivers available at http://jdbc.postgresql.org/download.html 
offer only JDBC Level 1 and JDBC Level 2 support for PSQL 7.1.3. Would 
that comply with Daisy's database "abstraction layer", or does Daisy 
need JDBC Level 3 support?

Here is the problem I have now:

For any PostgreSQL JDBC driver version I used (7.1-1.2 or 7.1-1.1 or 
even the 7.4 shipped with Daisy), I get the following very same exception:

postgres at quark-vm:/usr/local/daisy/openjms/bin# ./dbtool.sh -create 
-config $OPENJMS_HOME/config/openjms.xml

Using OPENJMS_HOME: /usr/local/daisy/openjms
Using JAVA_HOME:    /usr/local/java/j2sdk1.4.2_07
Using CLASSPATH:    
/usr/local/daisy/lib/postgresql/jars/postgresql-7.1-jdbc1.2.jar:/usr/local/daisy/openjms/lib/openjms-0.7.6.1.jar
16:16:26.023 ERROR [main] - 
org.exolab.jms.persistence.PersistenceException: Database does not 
support type=varchar(20)
org.exolab.jms.persistence.PersistenceException: Database does not 
support type=varchar(20)
    at org.exolab.jms.tools.db.SchemaBrowser.getType(SchemaBrowser.java:188)
    at org.exolab.jms.tools.db.RDBMSTool.getSQLType(RDBMSTool.java:266)
    at org.exolab.jms.tools.db.RDBMSTool.create(RDBMSTool.java:159)
    at org.exolab.jms.tools.db.RDBMSTool.create(RDBMSTool.java:105)
    at org.exolab.jms.tools.db.DBTool.create(DBTool.java:142)
    at org.exolab.jms.tools.db.DBTool.main(DBTool.java:256)

I am usure about the meaning of the exception. PostgreSQL certainly 
supports VARCHAR columns!

What could be wrong? How should I interpret that exception?

Kind regards
-- Olivier


==========================================
Here some details of the operations I made:

Downloaded daisy-1_2_0-pre3.tgz and followed installation instructions 
from http://new.cocoondev.org/daisy/docs/13.html.

Did not "GRANT ALL ON openjms.* TO openjms...", but instead created 
superusers 'openjms' and 'daisy' with:

PSQL -U postgres testdb
CREATE USER openjms WITH PASSWORD 'openjms' CREATEDB CREATEUSER;
CREATE USER daisy WITH PASSWORD 'daisy' CREATEDB CREATEUSER;

and then created the databases:

psql -U openjms testdb
CREATE DATABASE openjms;

psql -U daisy testdb
CREATE DATABASE daisyrepository;

I configured $OPENJMS_HOME/config/openjms.xml like this:

  <DatabaseConfiguration>
    <RdbmsDatabaseConfiguration
      driver="org.postgresql.Driver"
      url="jdbc:postgresql://localhost/openjms"
      user="openjms" password="openjms"
      maxActive="10" maxIdle="5" evictionInterval="3600"
      testQuery="select current_date" />
  </DatabaseConfiguration>

  also added <AdministeredDestinations>...</AdministeredDestinations> 
and <SecurityConfiguration ... /> as per daisy/docs/13.html

  and removed all trailing ^M on end of lines.