3. 5-7 seconds waiting while Tomcat finds that my webapp deployed
files are changed
If You run quartz it can look in a shorter time if Your webapp
deployed or not.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.ap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 4/19/2009 2:57 PM, André Warnier wrote:
> There must exist a more efficient mechanism for [redeploying webapps in
> Tomcat].
> One should probably check how the Tomcat Manager deploys an application
> on-demand, and use the same mechanism e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andre-John,
On 4/19/2009 7:25 PM, Andre-John Mas wrote:
> This is one reason I would like to see a "file change" listener as
> standard in Java.
You'd have to wait for a "file change" listener as standard in an OS, too.
> The idea is that for system
On Sun, Apr 19, 2009 at 9:43 PM, Caldarale, Charles R
wrote:
>
> How about pointless? Somewhat akin to debating the number of angels that can
> dance on the head of a pin.
>
Why pointless? The answer is obvious: 42
scnr...
Gregor
--
just because your paranoid, doesn't mean they're not after y
On 19-Apr-2009, at 14:57, André Warnier wrote:
Hi.
I am far from being the specialist here, but my inner application
designer core revolts at the idea of having a thread in Tomcat busy
at nothing else but checking 86,400 times a day, just in case you
redeploy an application from time to
> From: André Warnier [mailto:a...@ice-sa.com]
> Subject: Re: 15 second for redeployment is to much
>
> I'm curious to see Chuck's reaction to this thread.
How about pointless? Somewhat akin to debating the number of angels that can
dance on the head of a pin.
- Chuc
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 (*.j
Hi.
I am far from being the specialist here, but my inner application
designer core revolts at the idea of having a thread in Tomcat busy at
nothing else but checking 86,400 times a day, just in case you redeploy
an application from time to time.
There must exist a more efficient mechanism fo
I have 10 seconds now instead of 15 with 2 of 3 options:
backgroundProcessorDelay="1"
antiJARLocking="true" backgroundProcessorDelay="1"/>
and
lazy-init for all beans.
Cool! thanks again.
Now I'm going to sleep, and will implement javac direct compilation
tomorrow.
Kees Jan Koster пишет:
Thanks, for reply Pid.
Hardware is fast enough 2 Gb RAM, 2 Ghz CPU dual core athlon 64.
Sorry, I did not get your message. What do you think is not meaningful?
Some times and need to redeploy webapp 10 times in 10 minutes.
Pid пишет:
Kees Jan Koster wrote:
Dear Khlystov,
1. 5 s
Thanks, Kees!
I'll implement your advices, and will reply with results.
Kees Jan Koster пишет:
Dear Khlystov,
1. 5 second (using maven) compile source ( usually it is 1 or 2 files )
2. 0 second copy *.class file into Tomcat/webapps
Stop using Maven for simple compiles and write a small she
Kees Jan Koster wrote:
> Dear Khlystov,
>
>> 1. 5 second (using maven) compile source ( usually it is 1 or 2 files )
>> 2. 0 second copy *.class file into Tomcat/webapps
>
> Stop using Maven for simple compiles and write a small shell script that
> just calls javac with the webapp's WEB-INF/cla
Dear Khlystov,
1. 5 second (using maven) compile source ( usually it is 1 or 2
files )
2. 0 second copy *.class file into Tomcat/webapps
Stop using Maven for simple compiles and write a small shell script
that just calls javac with the webapp's WEB-INF/classes as output dir.
3. 5-7 s
13 matches
Mail list logo
