Fix for step 3. Don't wait for Tomcat to detect changes. See
http://tomcat.apache.org/tomcat-6.0-doc/manager-howto.html or use
org.apache.catalina.ant.ReloadTask (which uses the manager). My compile command
automaticly calls this after a succesful compile.
Another tip: test business logic (*.java) with junit. Don't start Tomcat for
it. And for GUI code you normaly don't need to redeploy your webapp. Tomcat can
dynamicly compile jsp and other template engines often can do that too.
Ronald.
Op zondag, 19 april 2009 18:56 schreef Khlystov Alexandr :>
Hello guys.
I can't fix my maven2+wicket application to be redeployed less than 15 seconds,
but I want it to take 5 seconds at least.
Could someone provide the fastest in the world practise of webapp on Tomcat
redeployment???
Precondition ( inital deployment): copy war dir with my webapp into tomcat
directory.
How redeployment time is spent:
1. 5 second (using maven) compile source ( usually it is 1 or 2 files )
2. 0 second copy *.class file into Tomcat/webapps
3. 5-7 seconds waiting while Tomcat finds that my webapp deployed
files are changed
4. 1 seconds takes to undeploy my webapp
5. 3-5 seconds takes to deploy ( really initialize Wicket & Spring
Beans frameworks with my data)
So it is too much I think.
Any ideas??
Thanks in advance.
--
Khlystov Alexandr
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
