I solved the problem. I didn't know yet that you have to check if your customized jsp files from a previous Dspace version have been updated in the newest Dspace version. Otherwise you won't have the newest code in your customized files jsp files. What I did was to remove the [dspace-source]/jsp/local/submit directory and rebuilt the wars again. Now I am able to submit new items to Dspace again.
Regards, Peter van Wonderen Am 13.08.2007 um 16:14 schrieb Peter van Wonderen: > > > Last week I installed Dspace 1.4.2. Since that moment submitting is > impossible because no data is written to our Postgresql database. > > We use: > > - java runtime version 1.5.0_06-b05 > > - PostgreSQL 8.1.9 > > - Postgresql-8.1-405.jdbc3 driver Looks fine. You might find an update for the JDBC driver if RedHat is up to date but that is probably not essential for your problem. If this is your last resort, you might walk through the Drivers Changelog here: <http://jdbc.postgresql.org/changes.html#version_8.1-406> <http://jdbc.postgresql.org/changes.html#version_8.1-407> <http://jdbc.postgresql.org/changes.html#version_8.1-408> <http://jdbc.postgresql.org/changes.html#version_8.1-409> <http://jdbc.postgresql.org/changes.html#version_8.1-410> But before you waste your time with that, try this: [cvoelker:~] cvoelker% psql Welcome to psql 8.2.4, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help with psql commands \g or terminate with semicolon to execute query \q to quit postgres=# \c dspace You are now connected to database "dspace". dspace=# \du List of roles Role name | Superuser | Create role | Create DB | Connections | Member of ----------+-----------+-------------+-----------+------------- +----------- dspace | no | no | yes | no limit | postgres | yes | yes | yes | no limit | (2 rows) dspace=# \dp Access privileges for database "dspace" Schema | Name | Type | Access privileges --------+--------------------------------+----------+------------------- public | bitstream | table | public | bitstream_seq | sequence | public | bitstreamformatregistry | table | public | bitstreamformatregistry_seq | sequence | public | bundle | table | public | bundle2bitstream | table | ... Is there something obviously different on both machines? There are many more options and you can also use pgAdmin to get better overview of the db if you are the GUI type of user like me. I wonder why there should be something different, but when taking a closer look and thinking about who things should look, I usually get a better understanding, get new ideas what to look for while investigating a problem. Bye, Christian ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
