cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Diana Shannon <shan...@apache.org>
Subject Re: Best way to start developing an application based on C2.1
Date Wed, 24 Jul 2002 14:23:05 GMT

On Wednesday, July 24, 2002, at 05:42  AM, Nicola Ken Barozzi wrote:

> Just a tip: if you install Cocoon jars in the WEB-INF/lib, you can add 
> your classes in WEB-INF/classes, and just restart Tomcat to use the new 
> classes. I do it also when developing Cocoon itself, since classes come 
> before of the libs in the classpath. ;-)


I received this helpful tip from Ivelin some time ago.

Use a build target of webapp-local to generate classes (faster than a 
war build). Instead of restarting Cocoon, however, use Tomcat's manager 
to install a path to the updated webapp, e.g.:
   
http://localhost:8080/manager/install?path=/cocoon&war=file:/cvs/c2-HEAD/xml-cocoon2/
build/cocoon/webapp

When you make a change that requires another webapp build, remove the 
webapp:
   http://localhost:8080/manager/remove?path=/cocoon

Then perform another webapp-local build and use the manager (as above) 
to install webapp again.

A few other notes:
- I typically disable all caching so I'm not sure if this works with 
caching enabled (i.e. without a clean work directory each time).
- To get manager working, you need to make sure you have a manager 
context specified in server.xml
- You need to add a <user name="manager"   password="ZZZ" roles="ZZZ" /> 
to <tomcat-users/> in tomcat-users.xml

Does anyone else use this?

-- Diana


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message