What I do is use JettyLauncher (jettylauncher.sourceforge.net) in debug mode
with caching turned off and as along as I don't go changing the public
classes too greatly, it will hotswap the code, meaning less restarts if
debugging the code.
----- Original Message -----
From: "Kent Tong" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, August 19, 2005 10:11 PM
Subject: Re: long startup time
I, for one, prefer to have all the bootstrapping/registry-building done
at
the beginning; especially before you have that crucial demo for a
potential
investor
Then a suite of automated tests will probably help more.
Are you perhaps asking for the option (some attribute in the "hivemind"
module) to allow for "lazy bootstrapping", so we who want the wait to be
localized still can be satisfied?
I'd like this to be a global JVM option. Tapestry is shipping with it
a lot of module descriptors. A tapestry user shouldn't be required to
edit those descriptors and build Tapestry again.
And, how long does this bootstrapping take for your specific (test)
project?
I have not seen a delay that would make me nor my team that anxious.
In Tapestry 4, for very simple test projects, the latency is about
several seconds (~5). In Tapestry 3, the latency is hardly noticable.
When testing, having a 5s latency every time the app is started
is hampering the code-test cycles.
--
Author of an e-Book for learning Tapestry
(http://www.agileskills2.org/EWDT)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
