cvs commit: jakarta-tomcat-4.0 build.properties.sample

billbarker2003/06/13 19:08:26 Modified:.build.properties.sample Log: Update to commons-fileupload-1.0-rc1 Revision ChangesPath 1.65 +4 -4 jakarta-tomcat-4.0/build.properties.sample Index: build.properties.sample ===

cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/servlets HTMLManagerServlet.java

billbarker2003/06/13 19:07:46 Modified:catalina/src/share/org/apache/catalina/servlets HTMLManagerServlet.java Log: Update to use the commons-fileupload-rc1 interface. Submitted by: Martin Cooper [EMAIL PROTECTED] Revision ChangesPath 1.16

running eXist XML database under tomcat-5.0.2

Hi, I am setting up a java web service using tomcat and eXist. I have successfully tested eXist as a standalone database. Now I want to integrate it into tomcat-5.0.2. I noticed when I start eXist as a standalone, using startup.sh, it says for tomcat, set openorb.home=/home/my_name/e

DO NOT REPLY [Bug 3888] - WebappClassLoader: Lifecycle error : CL stopped

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug

Servlets, Threading, and Memory

I'm experiencing a strange problem with a web application I'm developing under Tomcat 4.1.18 and am looking for information on how Tomcat handles threading and memory/variable scoping for servlets. I have a servlet that pulls data from a DB and generates graphs. On a given page sent the client bro

DO NOT REPLY [Bug 20770] New: - Admin Tool removes "workDir" attribute from "context"

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 15672] - DBCP doesn't work on Tomcat 4.1.18 with Oracle JDBC driver

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 11128] - ServletContext memory leak

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 20758] - Memory Leak in Classloader/Manager deploy/undeploy

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 10026] - manager/stop and manager/remove

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 20758] New: - Memory Leak in Classloader/Manager deploy/undeploy

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 10026] - manager/stop and manager/remove

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 10026] - manager/stop and manager/remove

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 20752] New: - Soft links to jars in a webapp causes IllegalArgumentException

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

cvs commit: jakarta-tomcat-jasper/jasper2/src/share/org/apache/jasper/compiler TldLocationsCache.java

remm2003/06/13 09:50:41 Modified:jasper2/src/share/org/apache/jasper/compiler TldLocationsCache.java Log: - Default to setting caches to false (rather than not), so that JAR locking does not occur. IMO it is a far more sensible default value for TC 5.

RE: Fixing the tomcat-catalina Gump failure

Howdy, +1 to port the patch ;) Yoav Shapira Millennium ChemInformatics >-Original Message- >From: Martin Cooper [mailto:[EMAIL PROTECTED] >Sent: Friday, June 13, 2003 2:48 AM >To: [EMAIL PROTECTED] >Subject: Fixing the tomcat-catalina Gump failure > >The Gump build for tomcat-catalina s

Re: Fixing the tomcat-catalina Gump failure

+1 to port the fileupload patch to the Tomcat 4.1 branch Bill Barker wrote: What is breaking in Gump is Tomcat-4.1.x. My patch fixed Tomcat 5.x. If Remy (as RM) is happy with using rc1 in TC 4.1.x (and no other committers object), I've got no problem porting the patch. The only reason that I've

RE: Problem displaying accents in Tomcat

There are two issues with character encoding. Firstly the charset used by Jasper for jsp source files, this is set in Tomcat web.xml. The default is UTF-8 and will effect jsp source files with special characters. From what I gather this isn't the problem, and only really causes a problem with far

Re: Problem displaying accents in Tomcat

> Yes, your asumptsion is right. I had apache before hooked to Tomcat. > Now the application is running with Tomcat 4.1.24 on its own. > The OS is linux, SUSE distro. > The character encoding it should be the default one I haven't specified > any. So it should be (iso-8859-1) ? > > Thanks >

Re: Problem displaying accents in Tomcat

Yes, your asumptsion is right. I had apache before hooked to Tomcat. Now the application is running with Tomcat 4.1.24 on its own. The OS is linux, SUSE distro. The character encoding it should be the default one I haven't specified any. So it should be (iso-8859-1) ? Thanks Manuel

RE: Problem displaying accents in Tomcat

This is really one for tomcat-user, but seeing as it's quiet... I assume you HAD Apache (HTTP Server) and Tomcat hooked up with mod_jk (or similar) previously and NOW you've just got Tomcat (4.1.24) on its own. Given that this is the case then something else has changed and is causing this proble

Problem displaying accents in Tomcat

Hi everyone, I have a problem with tomcat 4.1.24 with displaying vowels with accents and special spanish characters such as ñ. The scenario is the following : - I have deployed a servlet application that accesses data on a MySQL database. The problem is that when displaying characters with

DO NOT REPLY [Bug 20738] - Session variable returns null in non-SSL page

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 20738] New: - Session variable returns null in non-SSL page

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: Fixing the tomcat-catalina Gump failure

Bill Barker wrote: What is breaking in Gump is Tomcat-4.1.x. My patch fixed Tomcat 5.x. If Remy (as RM) is happy with using rc1 in TC 4.1.x (and no other committers object), I've got no problem porting the patch. The only reason that I've not done it is that there hasn't been a decision on the l

Re: Fixing the tomcat-catalina Gump failure

What is breaking in Gump is Tomcat-4.1.x. My patch fixed Tomcat 5.x. If Remy (as RM) is happy with using rc1 in TC 4.1.x (and no other committers object), I've got no problem porting the patch. The only reason that I've not done it is that there hasn't been a decision on the list as to the versi