TDK example application - failure at login screen

[Roger Ackroyd <ma...@ackroyd.freeserve.co.uk>]

Hi All
Have installed and built a sample Turbine application using TDK called newapp according to TDK HowTo.
The database is postgresql 7.3.3 with correct JDBC driver for that version.
The ant init target has built and populated the tables. 
There is an entry created for the turbine user/password in the db. 
When the user/password pair is submitted via the Turbine Data Manager login screen, the attached exception is thrown.
It is serving the logon screen Ok. 
The site pages navigation logic appears to be rendered and brokered Ok. 
Clearly a problem at db interface but it worked fine in order to generate and populate those tables with self same settings.
Can anyone throw some light on this please.
Thanks
Roger

RE: TDK example application - failure at login screen

[Lee Grey <le...@mindspring.com>]

Looks like a macro substitution problem in one of your build.properties
files:

31265 [HttpProcessor[8080][4]] ERROR util.BasePeer  -
org.apache.torque.TorqueEx
ception: Backend start-up failed: FATAL:  Database "${databaseUser}" does
not ex
ist in the system catalog.

Maybe that should be ${torque.databaseUser} or something along those lines.

Good luck,
Lee
  -----Original Message-----
  From: Roger Ackroyd [mailto:maven@ackroyd.freeserve.co.uk]
  Sent: Monday, August 04, 2003 2:09 PM
  To: Turbine Users List
  Subject: TDK example application - failure at login screen


  Hi All
  Have installed and built a sample Turbine application using TDK called
newapp according to TDK HowTo.
  The database is postgresql 7.3.3 with correct JDBC driver for that
version.
  The ant init target has built and populated the tables.
  There is an entry created for the turbine user/password in the db.
  When the user/password pair is submitted via the Turbine Data Manager
login screen, the attached exception is thrown.
  It is serving the logon screen Ok.
  The site pages navigation logic appears to be rendered and brokered Ok.
  Clearly a problem at db interface but it worked fine in order to generate
and populate those tables with self same settings.
  Can anyone throw some light on this please.
  Thanks
  Roger