On Sat, Jul 3, 2010 at 7:08 PM, Christopher Schultz
wrote:
> Heck, you can
> even use a single class that is a servlet but also implements
> ServletContextListener, and have everything in one class.
Setting up a case study for a "Real-life Refactoring" course? :-)
--
Hassan Schroeder
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric,
On 6/28/2010 11:37 PM, Eric P wrote:
> I've been loading up my web.xml with context and init params for my
> first app, but I'm thinking at some point it'd be nice to tweak these
> values on the fly while the app is running.
>
> What are some g
Just my comments on the dispatching idea proposed below...
If smooth processing with no freeze-time is important, I'm assuming there is
also some sort of cluster/high-availability functionality. If this is the
case, you are already running at least two Tomcats on different servers, and
using some
Eric P wrote:
So it makes sense to go into what "disruption" means. I'm not 100% sure
about the following, it would be good if a tomcat heavyweight would
confirm/refute what I say.
When you initiate a webapp reload, Tomcat waits for requests that have
already started processing to terminate. Thi
So it makes sense to go into what "disruption" means. I'm not 100% sure
about the following, it would be good if a tomcat heavyweight would
confirm/refute what I say.
When you initiate a webapp reload, Tomcat waits for requests that have
already started processing to terminate. This ensures that
Eric.
>>
>> Would making your servlet reload all application vars not be akin to
>> simply
>> reloading your servlet altogether, by changing context/init params in your
>> web.xml or context.xml?
>>
>>
> Do you mean "reloading your 'applicati
Shay,
Forgive all potential newbness in my responses below. I'm still learning this
stuff.
Shay Rojansky wrote:
Hi Eric.
Would making your servlet reload all application vars not be akin to simply
reloading your servlet altogether, by changing context/init params in your
web.x
Hi Eric.
Would making your servlet reload all application vars not be akin to simply
reloading your servlet altogether, by changing context/init params in your
web.xml or context.xml?
If you really want to avoid an application reload, why not just have your
app read its values from a properties
I've been loading up my web.xml with context and init params for my first app, but I'm thinking at some point it'd be
nice to tweak these values on the fly while the app is running.
What are some good practices to accomplish this?
I'm leaning towards storing all application variables in a datab
