Hi, I got your point. Thanks.
And I will continue to read the installation notes. thanks & rgds, --- Upayavira <[EMAIL PROTECTED]> wrote: > yangontha Maung wrote: > > >Hi, > > > >Thanks for your guidance. > > > >But I have tried this > >./cocoon.sh servlet & > > > >But it is still listening for something and the > >command prompt did not come back. > > > > > Ah, it does. But you've also got your output showing > too. You can still > type commands amidst the flow of Cocoon messages. > > That's why I suggested ./cocoon.sh servlet > > cocoon.log & > > That way, all output goes to a file, and you can > still use your console > without the interference of Cocoon's messages. > > >At the same time, I would like to ask another > thing. > >All along I thought that I am running cocoon over > >Tomcat. Could you guide me where I can learn on how > to > >run for production on Tomcat? > > > > > Look at > http://cocoon.apache.org/2.1/installing/index.html > > Regards, Upayavira > > >thanks, > > > >Here is the message after using &... > > > > > >[EMAIL PROTECTED] cocoon]# ./cocoon.sh servlet & > >[1] 3570 > >./cocoon.sh: using /usr/local/cocoon/build/webapp > as > >the webapp directory > >[EMAIL PROTECTED] cocoon]# -------------------- 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:52:57.382 EVENT Checking Resource aliases > >18:52:58.134 EVENT Starting Jetty/4.2.14 > >18:52:59.038 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:53:09 > >_SGT_2004 started. > >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:53:09.776 EVENT Started SocketListener on > >0.0.0.0:8888 > >18:53:09.777 EVENT Started > >[EMAIL PROTECTED] > >Sat Apr 17 18:53:10 SGT 2004 Listening for > connections > >... > > > > > >+++++++++++++++++++++ > >--- Upayavira <[EMAIL PROTECTED]> wrote: > > > > > >>yangontha Maung wrote: > >> > >> > >> > >>>Hi, > >>> > >>>I am using cocoon 2.1.4 on Red Hat Linux Server > >>> > >>> > >>using > >> > >> > >>>Tomcat 4.0.17. > >>> > >>> > >>> > >>> > >>You're not using Tomcat, you're using the Jetty > >>built into Cocoon. > >> > >>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 > === message truncated === __________________________________ 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]
