Hi:
If and when JDK 1.4 becomes the minimum platform
for Tomcat, the following must be kept in mind:
The java.util.logging framework provides a global
namespace that by default is tied to the system
classloaders. J2EE apps should modify this so that
the java.util.logging namespace is specific o
Hi:
I posted this in the tomcat-user but got no replies. I
thought tomcat developers read that list ?
Anyway, here's the problem:
Jsp's unders tomcat 4.1.30 return an empty
request.getInputStream().
If you _don't_ call request.getInputStream() in
your jsp but do call request.getReader(), an
in
>"Yoav Shapira" wrote thusly:
>I saw your message on tomcat-user. Several other
>Tomcat developers also follow that list. I
personally
>looking at the stack trace chose to discard your
>message for a few reasons:
You reply is retarded; more signifantly you are not
and
have never been a core deve
> Bill Barker wrote:
> I tested your report on TC 5 and the JKCoyote
> connector, and it works perfectly.
But why didn't you test on 4.1.30 ? Are you saying
this
bug does _not_ exist in the stable, widely used 4.1.30
release ? If not, that would be quite interesting
because tomcat is a java progra
>M.Hockings wrote:
>I use TC5 for my own stuff and WebSphere at work, why
>would I wish to install the older TC4? My ISP moved
>from TC4 to TC5 a while ago. Your note indicates
>4.1.30 and beyond, so 5.0.25 is a valid test for
>"beyond" is it not?
Yup. You're right about that. Although I meant
Hi all:
I am not sure if the following is a bug or mandated
by the spec, but if it _is_ a bug, it's quite serious:
Tomcat 4.1.30 looses all request data if the jsp that
is called is recompiled on the server side. That is
to say, the recompiled jsp sees an request with no
POST parameters at all !
