I also think it would be good idea to require Jasper's JspServlet still
function properly if used in Tomcat 3.3, even though Tomcat 3.3 now uses
an interceptor to manage JSP compilation. (Jasper is still used for
translation to servlet source, but the interceptor controls the
rest).
+1
(We u
Costin / 3.x advocates,
I've read the catalina overview by Craig, and the link that Costin
provided. Appologies if I haven't grasped enough of the designs as yet,
still need to spend more time reading the source code. I'm just wondering
about the benefits of the designs.
As far as I can see, 3.x
> Whoever wants to develop on tomcat 4 does so.
> Whoever wants to develop on tomcat 3 does so.
+1
Eventually a winning container will emerge. Forcing people to abandon the
current, production release will not work - they'll just go elsewhere, that
won't help anyone. If everyone concentrates
Is that \r\n in the body of the JSP or are you talking about the HTTP
headers / chunk lines ?
HTTP mandates \r\n for header and chunk count delimiters.
[EMAIL PROTECTED] on 20/12/2000 04:13:28
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
cc: [EMAIL PROT
We're using Jasper (for a number of reasons) inside Weblogic, and have seen
similar problems, but only intermittently -- usually either at startup or
during heavy load testing. I put a JspFactory.setDefaultFactory() call
in our code to try to force Jasper (rather than allow Weblogc to sneak
The type is javax.servlet.request.X509Certificate[] ?? ie an array not a
single instance..
[EMAIL PROTECTED] on 18/12/2000 05:03:48
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED] (bcc: Ken X Horn)
Subject: RE:RE: Réf. : RE: X509 client certificate (
