Re: Tomcat documentation issue

on 1/5/2001 9:58 PM, "Ted Husted" <[EMAIL PROTECTED]> wrote: > On 1/6/2001 at 3:58 AM Paulo Gaspar wrote: >> Some of the things that Tomcat is said to support (like SSL, > embedding and extending Tomcat) require a load of investigation FROM > EACH PERSON that tries to use it because there is not

RE: Tomcat documentation issue

On 1/6/2001 at 3:58 AM Paulo Gaspar wrote: > Some of the things that Tomcat is said to support (like SSL, embedding and extending Tomcat) require a load of investigation FROM EACH PERSON that tries to use it because there is not even a good pointer on where to start digging. It would be helpful

[ANNOUNCEMENT] Tomcat 4.0 Beta 1

The newest release of Tomcat 4.0, beta 1, is now available at the Jakarta web site: http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0-b1/ This release is the first in a series of betas that will lead to a production quality release of Tomcat 4.0 in the near future. At the same ti

Re: cvs commit: jakarta-tomcat-4.0/webapps/ROOT index.html

on 1/5/2001 9:52 PM, "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote: > Oh, I believe you just fine :-). And the record will show that I've been > pretty responsive to those bug reports, too. :-) :-) Yes and that is MOST appreciated. This is yet another shining example of why Open Source Works

Re: cvs commit: jakarta-tomcat-4.0/webapps/ROOT index.html

Jon Stevens wrote: > on 1/5/2001 8:52 PM, "Craig R. McClanahan" <[EMAIL PROTECTED]> > wrote: > > > That is not a provably correct assertion, given that it works on every test > > case > > I have concocted so far. > > > > Even if there is something in Turbine that makes it not work, that can be >

Re: cvs commit: jakarta-tomcat-4.0/webapps/ROOT index.html

on 1/5/2001 8:52 PM, "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote: > That is not a provably correct assertion, given that it works on every test > case > I have concocted so far. > > Even if there is something in Turbine that makes it not work, that can be > dealt > with subsequent to b1. It

Re: cvs commit: jakarta-tomcat-4.0/webapps/ROOT index.html

Jon Stevens wrote: > on 1/5/2001 8:13 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > > Update version numbers for 4.0-beta-1. > > Are we *really* ready for a b1 release? I think that the fact that sessions > get lost when the classloader reloads is a pretty big bug that should get > resol

Re: cvs commit: jakarta-tomcat-4.0/webapps/ROOT index.html

on 1/5/2001 8:13 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Update version numbers for 4.0-beta-1. Are we *really* ready for a b1 release? I think that the fact that sessions get lost when the classloader reloads is a pretty big bug that should get resolved before b1 is released. -jon

cvs commit: jakarta-tomcat-4.0/webapps/ROOT index.html

craigmcc01/01/05 20:13:02 Modified:catalina/src/share/org/apache/catalina Globals.java webapps/ROOT index.html Log: Update version numbers for 4.0-beta-1. Revision ChangesPath 1.17 +5 -5 jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/

RE: Tomcat documentation issue

> -Original Message- > From: Jon Stevens [mailto:[EMAIL PROTECTED]] > Sent: Saturday, January 06, 2001 04:16 > > Because it isn't my itch to scratch. The software works fine for me and I > understand it perfectly well. Community driven! > I make time to correct. I haven't flamed you at

Re: Tomcat can be shutdown by ANYONE.

On Fri, 5 Jan 2001, Jon Stevens wrote: > on 1/5/2001 7:00 PM, "Nick Bauman" <[EMAIL PROTECTED]> wrote: > > > Permissions 500 and ownership as nobody on the shutdown script should do > > it. In an rc script you can change ownshership before booting the server > > like so: > > > > echo "/usr/loca

Re: Tomcat can be shutdown by ANYONE.

on 1/5/2001 7:00 PM, "Nick Bauman" <[EMAIL PROTECTED]> wrote: > Permissions 500 and ownership as nobody on the shutdown script should do > it. In an rc script you can change ownshership before booting the server > like so: > > echo "/usr/local/jakarta-tomcat-3.2/bin/startup.sh &" | su nobody >

Re: Tomcat documentation issue

on 1/5/2001 6:58 PM, "Paulo Gaspar" <[EMAIL PROTECTED]> wrote: > Why do I have the feeling you are always "against"? > Is "being constructive" OUT? Is making suggestions for work for other people to do considered being constructive? In a volunteer organization, I don't think so. > Why don't YOU

Re: Tomcat can be shutdown by ANYONE.

Permissions 500 and ownership as nobody on the shutdown script should do it. In an rc script you can change ownshership before booting the server like so: echo "/usr/local/jakarta-tomcat-3.2/bin/startup.sh &" | su nobody Works dandy over here. On Fri, 5 Jan 2001 [EMAIL PROTECTED] wrote: > I ha

RE: Tomcat can be shutdown by ANYONE.

AFAIK from answers to similar postings, a Tomcat server accepts as valid any shutdown request coming from the same machine where it is running. Remember that the shutdown request is just another request sent trough sockets. All the server can check is the address it came from. I think (you sho

RE: Tomcat documentation issue

Jon, Why do I have the feeling you are always "against"? Is "being constructive" OUT? Why don't YOU do that documentation work? - Are you busy? - Have other priorities? Guess what: me too! We both have that same problem, but: - I still make time for some suggestions; - You still make tim

cvs commit: jakarta-tomcat-4.0/tester/web/WEB-INF web.xml

craigmcc01/01/05 18:38:13 Modified:tester/src/bin tester.xml tester/web/WEB-INF web.xml Added: tester/src/tester/org/apache/tester Forward01.java Include01.java tester/web Forward01.txt Include01.txt Log: Add unit tests t

Re: cvs commit: jakarta-tomcat/src/share/org/apache/jasper/compiler Compiler.java

"Scott M. Stirling" wrote: > On 05 Jan 2001 16:35:09 -0800, Hans Bergsten wrote: > > "Scott M. Stirling" wrote: > > > 1. Doesn't it seem a bit sloppy to leave a bunch of classes loaded that > > > will never get dumped unless the server is shutdown? Just a matter of > > > elegance, I suppose. > >

Re: cvs commit: jakarta-tomcat/src/share/org/apache/jasper/compiler Compiler.java

"Scott M. Stirling" wrote: > > On 05 Jan 2001 16:35:09 -0800, Hans Bergsten wrote: > > "Scott M. Stirling" wrote: > > > 1. Doesn't it seem a bit sloppy to leave a bunch of classes loaded that > > > will never get dumped unless the server is shutdown? Just a matter of > > > elegance, I suppose. >

Re: cvs commit: jakarta-tomcat/src/share/org/apache/jasper/compiler Compiler.java

On 05 Jan 2001 16:35:09 -0800, Hans Bergsten wrote: > "Scott M. Stirling" wrote: > > 1. Doesn't it seem a bit sloppy to leave a bunch of classes loaded that > > will never get dumped unless the server is shutdown? Just a matter of > > elegance, I suppose. [Hans Bergsten] > Yes, it does. But AFA

Re: cvs commit: jakarta-tomcat/src/share/org/apache/jasper/compiler Compiler.java

"Scott M. Stirling" wrote: > > OK, I am thinking this is a pretty good idea now too, since seeing your > and Marc's emails. My last two thoughts on the matter (just playing Devil's > advocate): That's good. It's easy to overlook some problems. > 1. Doesn't it seem a bit sloppy to leave a bun

Re: cvs commit: jakarta-tomcat/src/share/org/apache/jasper/compiler Compiler.java

OK, I am thinking this is a pretty good idea now too, since seeing your and Marc's emails. My last two thoughts on the matter (just playing Devil's advocate): 1. Doesn't it seem a bit sloppy to leave a bunch of classes loaded that will never get dumped unless the server is shutdown? Just a mat

Tomcat can be shutdown by ANYONE.

I have tried to run Tomcat 3.2.1 as nobody then on another shell login as my id ( eg barrow ), and run TOMCAT_HOME/bin/shutdown.sh. I can successfully bring tomcat. I also tried to run Tomcat 3.2.1 as root and I can also shutdown Tomcat 3.2.1 as my id ( eg. barrow ). Unless I did my configurati

Re: cvs commit: jakarta-tomcat/src/share/org/apache/jasper/compiler Compiler.java

Scott Stirling wrote: > > I agree with Craig. > > The ability to run JSP apps without any source JSPs must be maintained > for app vendors who want to ship without source code. Not sure if this > patch would interfere with that or not. It shouldn't; if you want to distribute JSP pages without

cvs commit: jakarta-tomcat/src/share/org/apache/jasper/runtime JspServlet.java

costin 01/01/05 15:56:37 Modified:src/share/org/apache/jasper/runtime Tag: J2EE_TOMCAT_30_1 JspServlet.java Log: Extra check for JSPs on Windows, similar with the one for static files. Revision ChangesPath No revision No

classloader 4.x (again)

Ok Craig, I'm testing out last nights snapshot and it appears as though the classreloading is working. Great! #1. It is figuring out the class has changed. #2. It is then calling the destroy method of Turbine #3. It is then acting like a new first request and calling the init() method on Turbine

AccessLog Helper class

Howdy! In the process of learning how valves work, I decided to create a minimal JDBCAccessLogValve. After finishing the first test version of this I noticed that I had pretty much copied/cut and pasted/stolen much of the functionality of the existing AccessLogValve into this new class, and star

RE: cvs commit: jakarta-tomcat/src/share/org/apache/jasper/compiler Compiler.java

> -Original Message- > From: Scott Stirling [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 05, 2001 3:58 PM > To: [EMAIL PROTECTED] > Subject: Re: cvs commit: > jakarta-tomcat/src/share/org/apache/jasper/compiler Compiler.java > > > I agree with Craig. > > The ability to run JSP apps w

Re: Tomcat documentation issue

on 1/5/2001 2:50 PM, "Paulo Gaspar" <[EMAIL PROTECTED]> wrote: > Well, that sure is part of many postings we see at the User lists. > But the fact is that there are still to many beginner/configuration > questions popping up that have no answer in any documentation. Then write a FAQ and point pe

Tomcat documentation issue

> -Original Message- > From: Jon Stevens [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 05, 2001 20:37 > > > on 1/5/2001 6:51 AM, "Paulo Gaspar" <[EMAIL PROTECTED]> wrote: > > > Tomcat has the same problem as Struts and most Open Source > > projects (it is not just an Apache thing): >

Re: cvs commit: jakarta-tomcat/src/share/org/apache/jasper/compiler Compiler.java

I agree with Craig. The ability to run JSP apps without any source JSPs must be maintained for app vendors who want to ship without source code. Not sure if this patch would interfere with that or not. A separate issue: if a user removes the source JSP, it may be OK to remove the JSP class file

Distributed Sessions 0.0.0.1

Title: Distributed Sessions 0.0.0.1 Hi, I couldn't find anything that would do distributed sessions, so I just cooked up a StandardSessionInterceptor for tomcat that saves session info to a database and has some limited failover capabilities. It's pretty neat. Get it at:     http://w

Re: [BUG] PropertyResourceBundle persisting outside servlet

Chris Longfield wrote: > Hello, > I am not sure if this is a bug or not. If not, perhaps you could explain why it >happens. I am using Apache-1.3.14, the jserv module 1.1.2, and tomcat 3.2.1 . The >HelloWorldExample uses a property resource bundle to fill in some data. If you >execute th

[BUG] PropertyResourceBundle persisting outside servlet

Hello, I am not sure if this is a bug or not. If not, perhaps you could explain why it happens. I am using Apache-1.3.14, the jserv module 1.1.2, and tomcat 3.2.1 . The HelloWorldExample uses a property resource bundle to fill in some data. If you execute the servlet once, and then remove

Re: cvs commit: jakarta-tomcat/src/share/org/apache/jasper/compiler Compiler.java

Marc Saegesser wrote: > The problem with that is that there is then *no* way to get rid of a JSP > page without manually deleting the .class files. This requires knowing > where they are stored *and* the class name mangling scheme. Neither of > these are intuitively obvious. > > The *only* thin

Re: [VOTES] Tomcat 4.0-Beta-1 and New CVS Repositories

on 1/5/2001 6:51 AM, "Paulo Gaspar" <[EMAIL PROTECTED]> wrote: > Tomcat has the same problem as Struts and most Open Source > projects (it is not just an Apache thing): > * NOT ENOUGH DOCUMENTATION * Sigh, this is a lame request now. We could write documentation until we are blue in the face and

RE: cvs commit: jakarta-tomcat/src/share/org/apache/jasper/compiler Compiler.java

The problem with that is that there is then *no* way to get rid of a JSP page without manually deleting the .class files. This requires knowing where they are stored *and* the class name mangling scheme. Neither of these are intuitively obvious. The *only* thing that the JSP developer really kn

Re: [BUG] Security violation in Tomcat 3.2.1 (was: [BUG] problems with downloading a file, previous JSP gets buffered and sent instead)

Stefán F. Stefánsson wrote: > > Sorry for the repost guys but I think this is serious enough for at > least one reply! > > In short, Tomcat is sending me a jsp file... that is to say, it's > sending me the "unprocessed" version of the JSP file, with code and > everything. The JSP file seems to

Re: cvs commit: jakarta-tomcat/src/share/org/apache/jasper/compiler Compiler.java

[EMAIL PROTECTED] wrote: > marcsaeg01/01/05 10:04:37 > > Modified:src/share/org/apache/jasper/compiler Tag: tomcat_32 > Compiler.java > Log: > Added a method to remove the generated .class file. This will be called > to remove generated files in the event

BugRat Report #707 has been filed.

Bug report #707 has just been filed. You can view the report at the following URL: REPORT #707 Details. Project: Tomcat Category: Feature Requests SubCategory: Enhancement Class: swbug State: received Priority: low Severity: non-crit

BugRat Report #698 was closed (apparently by: Marc Saegesser)

Report #698 was closed by Person #0 Synopsis: tomcat still allows viewing of a jsp even after the jsp file has been removed from webspace. (logged in as: Marc Saegesser) - To unsubscribe, e-mail: [EMAIL PROTECTED] For addi

cvs commit: jakarta-tomcat/src/share/org/apache/jasper/servlet JspServlet.java

marcsaeg01/01/05 10:09:10 Modified:src/share/org/apache/jasper/servlet Tag: tomcat_32 JspServlet.java Log: If the JSP page can't be found have the compiler remove any previously generated .class file. This will happen if a JSP page is removed after it ha

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

marcsaeg01/01/05 10:07:22 Modified:src/share/org/apache/jasper/compiler Tag: tomcat_32 JspCompiler.java Log: Added test to isOutDated() to check for the existence of the JSP page in addtion to checking the timestamps. If the JSP page has been removed a 4

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

marcsaeg01/01/05 10:04:37 Modified:src/share/org/apache/jasper/compiler Tag: tomcat_32 Compiler.java Log: Added a method to remove the generated .class file. This will be called to remove generated files in the event that the associated JSP page is removed

Access Control Exception Error!

we r trying to start the Tomcat programmatically by using EmbeddedTomcat .we followed the sequence of steps that are mentioned in EmbeddedTomcat program. In this process we r trying to get the contexts for each directory in the webapps folder. we also modified the "tomcat.policy" file by setting

BugRat Report #706 has been filed.

Bug report #706 has just been filed. You can view the report at the following URL: REPORT #706 Details. Project: Jasper Category: Bug Report SubCategory: New Bug Report Class: swbug State: received Priority: low Severity: non-critica

BugRat Report #705 has been filed.

Bug report #705 has just been filed. You can view the report at the following URL: REPORT #705 Details. Project: Tomcat Category: Bug Report SubCategory: New Bug Report Class: swbug State: received Priority: high Severity: critical C

RE: [VOTES] Tomcat 4.0-Beta-1 and New CVS Repositories

This is exactly what the 4.1 repository is for. If the 4.0 and 4.1 were going to reside in the same repository then branching would be appropriate, but the proposal was to move all new feature development into a new repository and there seem to be enough votes for that to happen. > -Original

RE: [VOTES] Tomcat 4.0-Beta-1 and New CVS Repositories

Marc Saegesser typed the following on 08:12 AM 1/5/2001 -0600 >I don't see the need for branch until Tomcat 4.0 Final is relased. Until >then, from a source control perspective, a beta release is no different than >a milestone release. In short, what code would ever be checked into "main" >that w

RE: [VOTES] Tomcat 4.0-Beta-1 and New CVS Repositories

Tomcat has the same problem as Struts and most Open Source projects (it is not just an Apache thing): * NOT ENOUGH DOCUMENTATION * In the case of the Jakarta projects the APIs documentation is usually quite satisfactory but the Introductions, HOW-TOs, User Guides, Architecture and other overv

redirecting and target

I used the following code to redirect and set the target to _top. response.setHeader("Window-target","_top"); response.setStatus(HttpServletResponse.SC_MOVED_TEMPORARILY); response.setHeader("Location", sPath); This works in the Netscape browser however in MS Internet Exp

RE: [VOTES] Tomcat 4.0-Beta-1 and New CVS Repositories

> (1) Tomcat 4.0 Beta 1 -0. I don't see the need for branch until Tomcat 4.0 Final is relased. Until then, from a source control perspective, a beta release is no different than a milestone release. In short, what code would ever be checked into "main" that would not also belong on the branch?

BugRat Report #703 has been filed.

Bug report #703 has just been filed. You can view the report at the following URL: REPORT #703 Details. Project: Tomcat Category: Bug Report SubCategory: New Bug Report Class: swbug State: received Priority: high Severity: critical C

RE: [VOTES] Tomcat 4.0-Beta-1 and New CVS Repositories

>I don't see any problem - there are 2 codebases - the >"original" tomcat ( >3.x ) and catalina ( 4.x ). You're in the project but imagine when a new user arrive and want to use a servlet engine ;-) The question will be must I use 3.2, 3.3, 4.0 or 4.1 ?-) A simple help rule could be : - If yo

[BUG] Security violation in Tomcat 3.2.1 (was: [BUG] problems with downloading a file, previous JSP gets buffered and sent instead)

Sorry for the repost guys but I think this is serious enough for at least one reply! In short, Tomcat is sending me a jsp file... that is to say, it's sending me the "unprocessed" version of the JSP file, with code and everything. The JSP file seems to get stuck in the OutputStream buffer of the

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

jiricka 01/01/05 01:26:07 Modified:src/share/org/apache/jasper/compiler Tag: tomcat_32 TagLibraryInfoImpl.java Log: Fixed incorrect reporting of JSP compilation errors in cases a tag library can not be found. Now the compilation error message includes a co