I guess that aspect of it comes down to a personal philosophy more than
anything else. I typically try to help things like this bubble up so the
knowledge can be shared and pain can be avoided in a proactive way instead of
waiting for others to learn for themselves. So that's why I'm asking
Hello,
as to my knowledge the modern containers do not encourage the usage of
shared data anymore, and this was the only possible problem cause
anyway:
The real root cause of this problem is that SHARED data (static
members on a class) is being shared across supposedly independent
applications.
Ray and crew
other than accomodating a main driver such as public static void main(String
args[]) is there any reason for declaring any method or variable as static?
an intelligent logger (log4j) could reconfigure the appenders to redeploy
CPU-intensive/memory-intensive/IO intensive
On 10/09/2010 13:29, Leon Rosenberg wrote:
Hello,
as to my knowledge the modern containers do not encourage the usage of
shared data anymore, and this was the only possible problem cause
anyway:
The real root cause of this problem is that SHARED data (static
members on a class) is being
The Apache Commons team is pleased to announce the release of
version 1.5.5 of Commons Pool. Commons Pool provides a general
purpose object pooling API, an implementation toolkit and some pool
implementations.
Version 1.5.5 is a patch release including bug fixes, documentation
improvements and
On 9/10/2010 9:15 AM, Martin Gainty wrote:
Ray and crew
other than accomodating a main driver such as public static void
main(String args[]) is there any reason for declaring any method or
variable as static?
Sure. If you have methods that are self-contained, i.e., use only
parameters or
Take Math.sin as an example. Should you have to instantiate a Math object
just to compute the sine?
On Fri, Sep 10, 2010 at 8:18 PM, Guy Rouillier guyr-...@burntmail.comwrote:
On 9/10/2010 9:15 AM, Martin Gainty wrote:
Ray and crew
other than accomodating a main driver such as public
