On Sun, 29 Jan 2006, Leon Rosenberg wrote:
| On 1/29/06, David Tonhofer, m-plify S.A. <[EMAIL PROTECTED]> wrote:
| > Another 2c: When doing Java, you may want to stay clear of J2EE. I have
| > heard it's the Wooly Mammoth framework and I have so far worked happily
| > without it. I recommend a loo
On Thu, 26 Jan 2006, Davide Romanini wrote:
| Il giorno mer, 25/01/2006 alle 11.12 -0800, Wade Chandler ha scritto:
|
| > Don't use shared libraries and you shouldn't have this
| > problem. If all of the statics are in your WEB-INF
| > directory then you won't have an issue with unloading
| > cl
| > It's a known problem caused by a lot of different
| > situations. It's sad
| > that a lot of important applications suffer of this
| > problem. I'm working
| > with Axis, and just trying to reload the bundled
| > webapp never release
| > the old WebappClassloader.
| >
| > I think this is seri
(Apparently sent this to the wrong address first time)
Hi!
I have a memory-leak.
That is, I can't start my full application and have unload-capability. If I
"comment out" (by adding 'if (false) { ... }') large chuncks of the system, I
manage to get it up, _and_ get it down again!
Currently,
Hi!
I have a memory-leak.
That is, I can't start my full application and have unload-capability. If
I "comment out" (by adding 'if (false) { ... }') large chuncks of the
system, I manage to get it up, _and_ get it down again!
Currently, pretty much the whole application have to be commented
On Tue, 10 Jan 2006, Oded Arbel wrote:
| On Tuesday, 10 ÿÿJanuary 2006 00:06, Endre Stølsvik wrote:
| > Enabling the RequestDumperValve in both 5.5.12 and 5.0.16 (!) messes
| > up the parsing of other-than-ISO-8859-1 incoming parameters.
| >
| > After using a rather huge bunch of hour
On Mon, 9 Jan 2006, Mark Thomas wrote:
| Endre Stølsvik wrote:
| > Enabling the RequestDumperValve in both 5.5.12 and 5.0.16 (!) messes up
| > the parsing of other-than-ISO-8859-1 incoming parameters.
| >
| > After using a rather huge bunch of hours, this came down as the result:
|
Enabling the RequestDumperValve in both 5.5.12 and 5.0.16 (!) messes
up the parsing of other-than-ISO-8859-1 incoming parameters.
After using a rather huge bunch of hours, this came down as the result:
when this "debug valve" is turned on, it seems to default to ISO-8859-1
when it parses and l
