You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by David Rosenstrauch <da...@dti.net> on 2001/11/02 16:22:09 UTC

Testing under cocoon

If this is available in an FAQ somewhere, please feel free to point me there, but I couldn't find anything.

Is there any way for me to test more efficiently under cocoon?  Currently my process is:

* run my build file to compile and deploy everything
* start tomcat
* test by pointing browser to web page and verifying results correct
* stop tomcat
* update/fix my code and stylesheets
* repeat


It looks to me like I need to keep starting/stopping tomcat so that Tomcat/Cocoon will reload the stylesheets and class files that I have changed.  Of course I'd prefer to not have to spend the time starting/stopping if I don't have to.

Any suggestions?


TIA!


DR


---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>


Re: Testing under cocoon

Posted by David Rosenstrauch <da...@dti.net>.
Simone and Steve,

Thanks for your answers!  A great help!


DR



At 11:06 AM 11/2/01 -0500, you wrote:
>David Rosenstrauch wrote:
> > 
> > If this is available in an FAQ somewhere, please feel free to point me there, but I couldn't find anything.
> > 
> > Is there any way for me to test more efficiently under cocoon?  Currently my process is:
>
>You can use Tomcat's manager app to reload your app without restarting
>Tomcat. First you have to set up a password for the manager role in
>tomcat-users.xml (maybe more, look at the tomcat docs), then you can
>reload by going to a URL like this:
>
>http://localhost:8080/manager/reload?path=/[your app]
>
>Should work, although you may have to specify reloadable=true in the
>Tomcat context for your app.
>
>Steve
>
>---------------------------------------------------------------------
>Please check that your question has not already been answered in the
>FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>
>To unsubscribe, e-mail: <co...@xml.apache.org>
>For additional commands, e-mail: <co...@xml.apache.org> 


---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>


Re: Testing under cocoon

Posted by Steve Gass <sg...@gass.com>.
David Rosenstrauch wrote:
> 
> If this is available in an FAQ somewhere, please feel free to point me there, but I couldn't find anything.
> 
> Is there any way for me to test more efficiently under cocoon?  Currently my process is:

You can use Tomcat's manager app to reload your app without restarting
Tomcat. First you have to set up a password for the manager role in
tomcat-users.xml (maybe more, look at the tomcat docs), then you can
reload by going to a URL like this:

http://localhost:8080/manager/reload?path=/[your app]

Should work, although you may have to specify reloadable=true in the
Tomcat context for your app.

Steve

---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>


Re: Testing under cocoon

Posted by Simone Gianni <si...@discoone.com>.
At 10.22 02/11/2001 -0500, you wrote:
>It looks to me like I need to keep starting/stopping tomcat so that 
>Tomcat/Cocoon will reload the stylesheets and class files that I have 
>changed.  Of course I'd prefer to not have to spend the time 
>starting/stopping if I don't have to.

If you just change XML or XSLT you can avoid restarting it all, it will 
reload it automatically. For changes in the sitemap, it is recompiled 
asynch. So you modify the site map, the point to a page (or reload it), it 
will display the old one, wait a few seconds, the reload it again and you 
get the new one.  In cocoon.xconf (but i could be wrong on this) there is a 
setting to make the sitemap regeneration synch ... this is not good for a 
production environment, but is very good for testing, since it recompiles 
the sitemap at the first get after it has changed.

If you change any class, like actions or similars, you can try to change 
the autoreload setting of tomcat, since this is handled by tomcat itself. 
To do this, in the server.xml file, you should add explicitly the cocoon 
context and set the auto-reload="true" attribute. This is documented in the 
server.xml file. Anyway, i have not tested this yet.

Also : starting and stopping tomcat/cocoon sometimes led on my computer to 
some strange things to happen : sometime it does not recompile something 
correctly, so i have to manually delete the %TOMCAT_HOME%/work/cocoon... 
directory.

Hope this helps.

Ciao, Simone



---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>