Ate Douma wrote:
[snipped...]
Did you encounter this problem right away after the first time starting up Tomcat?
Yes.
Try to stop and Tomcat again and see if the problem is resolved then.
Nope, it still did it...
This error can be caused if Tomcat deployed a portlet application before Jetspeed had had a change of telling it so. Disabling Tomcat autodeploy would solve it in that case. That is described (as last) in the Deployment Optimization
section in the readme.
I started the database and then ran ant so it did what ever it would have done on a different database. I then had to start Tomcat twice, the first time it just threw exception after exception. So I turned off autodeploy in the server.xml and restarted and it now works.
Should I have had to run Ant or does the default database not come with the schema fully defined...?
Thanks,
-- Bob Arnott
Software Developer Autonomy Systems Ltd. Cambridge Business Park Cowley Road Cambridge CB4 0WZ
T: +44 (0) 1223 448 000 F: +44 (0) 1223 448 001 http://www.aungate.com/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
