From: Dannes W. <di...@gm...> - 2006-08-08 17:13:15
|
hi, On 8/8/06, Latham, SE (Sue) <S.E...@rl...> wrote: > Anyone using the 1.1 .war on its own under linux/tomcat? sure..... > I've unpacked this manually to a webapps/exist directory. I haven't > installed the corresponding .jar version at all (do I need to?). No, but what you have done is not the best thing to do. I would like to suggest you to use the manager interface (http://localhost:8080/manager/html). Down under on the page you'll see a "WAR file to deploy" button. When uploading a war file this way, it is guaranteed that the deployed war file works. Internally the war file is extracted to a directory called 'exist' (when you renamed the war file to exist.war) When you unzip the war file manually, especially under *n*x when the server is installed as root, you might encounter problems. Copying exist.war to /usr/local/webapps/exist.war is sufficent too. Restart tomcat and you are done.... The server extracts all files for you..... > $ java -jar WEB-INF/lib/start.jar client -l Don't do this. Start the client via Java Webstart (see http://localhost:8080/exist )...... I expect error messages when you start the application is started like this. It *is* possible, but........ too difficult. > WARN: The following JAR file entries from 'org/exist/start/start.config' > aren't available (this may NOT be a problem): this is a problem indeed.... > log4j:WARN Continuable parsing error 1 and column 181 > log4j:WARN Document root element "log4j:configuration", must match DOCTYPE > root "null". warnings are not errors.... Does the application start? if so ignore all messages :-P regards Dannes -- # Dannes Wessels # The Netherlands # # Jabber / ICQ / MSN / AIM / Yahoo / google.com/talk # |