mod_webapp + Tomcat 4 + Apache
Hi, When would the mod_webapp/Tomcat4/Apache combination be ready for production use? Is anyone using this combination already? In the release notes of Beta 7 it is stated that the combination does work but there are some limitations pertaining to basic authentication. I'm using form authentication so that limitation is not an issue. Am I correct in saying that Tomcat 4 is already better than Tomcat 3 despite it not being labeled Final yet (because the Servlet 2.3 specs haven't yet been finalized)? I don't want to learn having to configure Tomcat 3 when the latest and greatest is just around the corner. Thanks -Laurens
Tomcat 4, making java:comp/env writable
Hi, Is there a way to make the java:comp/env JNDI context (and its subcontexts) writable in a release build of Tomcat 4? When I attempt to bind an object I get a read-only exception. I have a servlet which runs at startup and makes some objects available via JNDI for later use. I *can* write to the root context (InitialContext) and retrieving objects stored there works fine. However, I strive to make my servlets and other classes as portable as possible. Resin (which I use for development but not deployment) only allows writing to the java:comp/env context. So I want to store objects in java:comp/env and below. In order for that to happen the context must be writable. Can anyone tell me if that is possible? Regards -Laurens
RE: Tomcat 4, making java:comp/env writable
Hi, I just read that java:comp/env is supposed to be read-only. Resin does not follow this rule. Tomcat's behaviour in this is correct. Disregard my question Regards -Laurens -Original Message- From: Laurens Fridael [mailto:[EMAIL PROTECTED]] Sent: maandag 27 augustus 2001 8:59 To: Tomcat mailing list Subject: Tomcat 4, making java:comp/env writable Hi, Is there a way to make the java:comp/env JNDI context (and its subcontexts) writable in a release build of Tomcat 4? When I attempt to bind an object I get a read-only exception. I have a servlet which runs at startup and makes some objects available via JNDI for later use. I *can* write to the root context (InitialContext) and retrieving objects stored there works fine. However, I strive to make my servlets and other classes as portable as possible. Resin (which I use for development but not deployment) only allows writing to the java:comp/env context. So I want to store objects in java:comp/env and below. In order for that to happen the context must be writable. Can anyone tell me if that is possible? Regards -Laurens
Tomcat 4, mod_webapp problem
Hi, I've managed to build mod_webapp on ourLinux machine.First Iencountered troubles with the APXS script of the current installation. I then installed the latest version of Apache (1.3.20) and still ran into difficulties. With a little modification of the apxs script (a hint from the Tomcat mailing archive) Icould finally build it. However, when I try to load mod_webapp into Apache (using LoadModule) I get this error message: "Cannot load /usr/local/apache/libexec/mod_webapp.so into server: /usr/local/apache/libexec/mod_webapp.so: undefined symbol: pthread_sigmask" Apparently there are still unresolved symbols, or my paths aren't set correctly. Can anyone give me a hint? I'm thinking of reinstalling Linux. The current installation is flaky at best but it worked alright for well over a year. Thanks -Laurens
Tomcat 4/Apache combination
Hi, Can anyone comment on the stability of the Tomcat 4 / Apache combination? Do the Apache module and the Tomcat 4 connector work well enough for production use? I know Tomcat 4 is still in beta state, but I'm willing to take the risk.The Servlet 2.3 Filter feature will be a great time-saver for my current project. Thanks -Laurens
