Hi,You're not using Tomcat, you're using the Jetty built into Cocoon.
I am using cocoon 2.1.4 on Red Hat Linux Server using
Tomcat 4.0.17.
This built in Jetty is intended for testing/evaluation, not for deployment.
If you want to start this version in the background, while learning, try just adding a & to the end of the command:
./cocoon.sh servlet &
You'll still get the stuff going to the screen, but you'll get your command prompt back.
Or: ./cocoon.sh servlet > cocoon.log &
so that the screen stuff goes to a log file.
Then, to see the contents of the log file, do:
tail -f cocoon.log
CTRL_C will get you out of that.
This is all Unix stuff really.
When you come to deploy your site, you're going to have to work out how to deploy Cocoon within a proper servlet container, either Tomcat, or the full Jetty distribution.
Regards, Upayavira
When I start the cocoon using ./cocoon.sh servlet There will be a few messages come out and the cocoon will be running. It is normal. But the starting command line screen hangs there and I have to use Ctrl C to shut down the cocoon server.
How can I just give the starting command and make the screen back to normal command prompt, so that I can carry on to use it for others?
Below is the messages....
(Also I cannot use the SHUTDOWN message to stop.. as mentioned there..)
rgds,
[EMAIL PROTECTED] cocoon]# ./cocoon.sh servlet ./cocoon.sh: using /usr/local/cocoon/build/webapp as the webapp directory -------------------- Loading -------------------- Processing repository: /usr/local/cocoon/tools/jetty/lib Adding jar: /usr/local/cocoon/tools/jetty/lib/jetty-4.2.14.jar Adding jar: /usr/local/cocoon/tools/jetty/lib/servlet-2.3.jar Processing repository: /usr/local/cocoon/lib/endorsed Adding jar: /usr/local/cocoon/lib/endorsed/xalan-2.5.2.jar Adding jar: /usr/local/cocoon/lib/endorsed/xercesImpl-2.6.1.jar Adding jar: /usr/local/cocoon/lib/endorsed/xml-apis.jar -------------------- Executing ----------------- Main Class: org.mortbay.jetty.Server 18:20:27.972 EVENT Checking Resource aliases 18:20:28.376 EVENT Starting Jetty/4.2.14 18:20:28.904 EVENT Started WebApplicationContext[/,/usr/local/cocoon/build/weba pp] INFO [main] (DatabaseImpl.java:183) - No configuration file specified, going wi th the default configuration WARN [main] (DatabaseImpl.java:210) - The database configuration file is not sp ecified and there was no xindice.db.home property set, so Xindice was unable to determine a database location. Database will be created relative to the current directory. INFO [main] (Database.java:331) - Database points to /usr/local/cocoon-2.1.4/db INFO [main] (DatabaseImpl.java:183) - No configuration file specified, going wi th the default configuration WARN [main] (DatabaseImpl.java:210) - The database configuration file is not sp ecified and there was no xindice.db.home property set, so Xindice was unable to determine a database location. Database will be created relative to the current directory. server.properties not found, using command line or default properties Opening database: /usr/local/cocoon-2.1.4/build/webapp/WEB-INF/db/cocoondb HSQLDB server 1.7.1 is running Use SHUTDOWN to close normally. Use [Ctrl]+[C] to abort abruptly context: /usr/local/cocoon-2.1.4/build/webapp INFO [main] (DirectSchedulerFactory.java:295) - Quartz scheduler 'Cocoon INFO [main] (DirectSchedulerFactory.java:298) - Quartz scheduler version: 1.2.3 INFO [main] (QuartzScheduler.java:327) - Scheduler Cocoon_$_Sat_Apr_17_18:20:36 _SGT_2004 started. Sat Apr 17 18:20:37 SGT 2004 Listening for connections ... WARN! *** JMS block is installed but jms client library not found. *** - For the jms block to work you must install and start a JMS server and place th e client jar in WEB-INF/lib. - The default server, OpenJMS is configured in cocoon.xconf but is not bundled w ith Cocoon. 18:20:37.405 EVENT Started SocketListener on 0.0.0.0:8888 18:20:37.406 EVENT Started [EMAIL PROTECTED]
__________________________________ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
