RE: Tomcat 3.3 repository changes

I'm starting to get a little more free time, and will try to put together a plan for Tomcat 3.3.2 in the next few weeks. AFAIK, there is little or no duplication between TC3.3.x's util classes and JTC's util classes. What was moved to JTC has been removed from TC3.3.x. Cheers, Larry > -Ori

Re: Tomcat 3.3 repository changes

On Fri, 2002-09-13 at 19:46, Henri Gomez wrote: > Now that we have mod_jk present on JTC, what about removing it from TC > 3.3.2 CVS ? +1 Bojan -- To unsubscribe, e-mail: For additional commands, e-mail:

RE: Tomcat 3.3 and 4.x tuning via command line

>There's a lot of power in what the task can do. >Here's a very >simple one that replaces the string "@port@" with the port number >specified by the "port" property: > > > > > > > > >In your template server.xml, you'd have a element >like this: > > > >Now, you just run "an

RE: Tomcat 3.3 and 4.x tuning via command line

On Fri, 8 Feb 2002, Craig R. McClanahan wrote: > > > > > > In your template server.xml, you'd have a element like this: > > > > Now, you just run "ant -Dport=8085" and you've replaced the port number. > Generalizing this to replace lots of properties is straightforward. W

RE: Tomcat 3.3 and 4.x tuning via command line

On Fri, 8 Feb 2002, GOMEZ Henri wrote: > Date: Fri, 8 Feb 2002 18:10:57 +0100 > From: GOMEZ Henri <[EMAIL PROTECTED]> > Reply-To: Tomcat Developers List <[EMAIL PROTECTED]> > To: Tomcat Developers List <[EMAIL PROTECTED]> > Subject: RE: Tomcat 3.3 and 4.x

RE: Tomcat 3.3 and 4.x tuning via command line

>I'm wondering whether we really need to build it in to Tomcat itself, >though. Can't you accomplish the same thing by using a little >Ant script >and run a or task? All this would require >is packaging >ant.jar along with Tomcat, or requiring users that need the facility to >download Ant th

RE: Tomcat 3.3 and 4.x tuning via command line

On Fri, 8 Feb 2002, GOMEZ Henri wrote: > Date: Fri, 8 Feb 2002 09:31:44 +0100 > From: GOMEZ Henri <[EMAIL PROTECTED]> > Reply-To: Tomcat Developers List <[EMAIL PROTECTED]> > To: Tomcat Developers List <[EMAIL PROTECTED]> > Subject: RE: Tomcat 3.3 and 4.x tunin

RE: Tomcat 3.3 - Cactus Issue

Ok. Thanks Costin. What I'll keep in mind is that it is complex ... ;-) -Vincent > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: 08 February 2002 00:28 > To: Tomcat Developers List > Subject: RE: Tomcat 3.3 - Cactus Issue > > O

RE: Tomcat 3.3 and 4.x tuning via command line

>> I don't know if the Eclipse configuration allows you to >> specify -D= in Tomcat's startup. If it does, >> I think a lot of this can be done in Tomcat 3.3.1 using >> parameter substitution. I have used in server.xml >> >> >> >> and included >> >> -Dhttp.port=8080 >> >> in the startup

RE: Tomcat 3.3 - Cactus Issue

On Thu, 7 Feb 2002, Vincent Massol wrote: > Last thing I'd like to confirm : When data is sent over a socket, it > will fill the socket buffer (at the client side) and then sending of > data will block until the server side reads from the socket buffer ? If The first part - I'm not sure. I expec

RE: Tomcat 3.3 - Cactus Issue

ginal Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: 07 February 2002 22:47 > To: Tomcat Developers List > Subject: RE: Tomcat 3.3 - Cactus Issue > > On Thu, 7 Feb 2002, Larry Isaacs wrote: > > > Many thanks for finding this. Not suprisingl

RE: Tomcat 3.3 - Cactus Issue

On Thu, 7 Feb 2002, Larry Isaacs wrote: > Many thanks for finding this. Not suprisingly Costin's > initial guess was correct. Fortunately I wasn't wrong > about one assumption, which was the reason for the failure > was that Tomcat 3.3 was too fast. Thanks again, to Costin. Well, given the am

Re: Tomcat 3.3 - Cactus Issue

See inline. - Original Message - From: "Vincent Massol" <[EMAIL PROTECTED]> To: "'Tomcat Developers List'" <[EMAIL PROTECTED]> Sent: Thursday, February 07, 2002 1:57 PM Subject: RE: Tomcat 3.3 - Cactus Issue > Hey thanks guys ! You'

RE: Tomcat 3.3 - Cactus Issue

On Thu, 7 Feb 2002, Vincent Massol wrote: > Are you saying that the logic in Tomcat is that prior to closing a > socket, all data is read first ? No, tomcat will just try to flush it's input buffers. We don't want to read all data - the servlet is supposed to process the request and decide if i

RE: Tomcat 3.3 - Cactus Issue

ht and then tag 3.3.1-beta1 and begin staging the beta1 release. Cheers, Larry > -Original Message- > From: Bill Barker [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 07, 2002 4:38 PM > To: Tomcat Developers List > Subject: Re: Tomcat 3.3 - Cactus Issue > > >

RE: Tomcat 3.3 - Cactus Issue

HTTP parameters are sent both in the URL _and_ in the body as POST data ? Thanks a lot -Vincent > -Original Message- > From: Bill Barker [mailto:[EMAIL PROTECTED]] > Sent: 07 February 2002 21:38 > To: Tomcat Developers List > Subject: Re: Tomcat 3.3 - Cactus Issue > >

Re: Tomcat 3.3 - Cactus Issue

ED]> Sent: Thursday, February 07, 2002 9:05 AM Subject: RE: Tomcat 3.3 - Cactus Issue > On Thu, 7 Feb 2002, Vincent Massol wrote: > > > The particularity of testPostMethod is that it sends information both in > > the URL (as parameters) and in the request BODY in POST form

RE: Tomcat 3.3 - Cactus Issue

> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 07, 2002 12:06 PM > To: Tomcat Developers List > Subject: RE: Tomcat 3.3 - Cactus Issue > > > On Thu, 7 Feb 2002, Vincent Massol wrote: > > > The p

RE: Tomcat 3.3 and 4.x tuning via command line

>It appears, for example, that the only thing you can override about a >connector is which port it's on. What happens if you want to override, >say, the maximum number of connections that your connector will accept >(the "maxProcessors" parameter on Tomcat 4's HttpConnector)? Right +1 for you he

RE: Tomcat 3.3 and 4.x tuning via command line

On Thu, 7 Feb 2002, Larry Isaacs wrote: > Date: Thu, 7 Feb 2002 07:40:21 -0500 > From: Larry Isaacs <[EMAIL PROTECTED]> > Reply-To: Tomcat Developers List <[EMAIL PROTECTED]> > To: 'Tomcat Developers List' <[EMAIL PROTECTED]> > Subject: RE: Tomca

RE: Tomcat 3.3 - Cactus Issue

On Thu, 7 Feb 2002, Vincent Massol wrote: > The particularity of testPostMethod is that it sends information both in > the URL (as parameters) and in the request BODY in POST form. > > Thus, there is some POST data sent ! Ok, then what really matters is who reads the body and how. Sorry for not

Re: Tomcat 3.3 and 4.x tuning via command line

On Thu, 7 Feb 2002, GOMEZ Henri wrote: > Date: Thu, 7 Feb 2002 09:28:01 +0100 > From: GOMEZ Henri <[EMAIL PROTECTED]> > Reply-To: Tomcat Developers List <[EMAIL PROTECTED]> > To: Tomcat Developers List <[EMAIL PROTECTED]> > Subject: Tomcat 3.3 and 4.x tuning via command line > > Hi to all, > >

RE: Tomcat 3.3 - Cactus Issue

Line 313: out.print(queryString.toString()); out.close(); -Vincent > -Original Message- > From: Larry Isaacs [mailto:[EMAIL PROTECTED]] > Sent: 07 February 2002 15:43 > To: Tomcat Developers List > Subject: RE: Tomcat 3.3 - Cactus Issue > > Thanks for the info. However,

RE: Tomcat 3.3 - Cactus Issue

lace I'm not looking where POST data is added as part of the client handling for this test? Cheers, Larry > -Original Message- > From: Vincent Massol [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 07, 2002 10:15 AM > To: 'Tomcat Developers List

RE: Tomcat 3.3 - Cactus Issue

> -Original Message- > From: Larry Isaacs [mailto:[EMAIL PROTECTED]] > Sent: 07 February 2002 14:16 > To: 'Tomcat Developers List' > Subject: RE: Tomcat 3.3 - Cactus Issue > > For the testPostMethod test, can you point me to where in > Cactus, the POST

RE: Tomcat 3.3 - Cactus Issue

age- > From: Vincent Massol [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 07, 2002 8:09 AM > To: 'Tomcat Developers List' > Subject: RE: Tomcat 3.3 - Cactus Issue > > > Sorry guys for not jumping in earlier. > > Here is some more informat

RE: Tomcat 3.3 and 4.x tuning via command line

sday, February 07, 2002 7:53 AM > To: Tomcat Developers List > Subject: RE: Tomcat 3.3 and 4.x tuning via command line > > > >I don't know if the Eclipse configuration allows you to > >specify -D= in Tomcat's startup. > > Yes you could set any VM and co

RE: Tomcat 3.3 - Cactus Issue

Costin, See inline > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: 05 February 2002 19:08 > To: Tomcat Developers List > Subject: Re: Tomcat 3.3 - Cactus Issue > > On Tue, 5 Feb 2002 [EMAIL PROTECTED] wrote: > > > Mo

RE: Tomcat 3.3 - Cactus Issue

TECTED]] > Sent: 05 February 2002 19:46 > To: Tomcat Developers List > Subject: RE: Tomcat 3.3 - Cactus Issue > > On Tue, 5 Feb 2002, Larry Isaacs wrote: > > > I looked for this and didn't find that there was any POST data > > sent and none was read. I certainly

RE: Tomcat 3.3 and 4.x tuning via command line

>I don't know if the Eclipse configuration allows you to >specify -D= in Tomcat's startup. Yes you could set any VM and commandline args. >If it does, >I think a lot of this can be done in Tomcat 3.3.1 using >parameter substitution. I have used in server.xml > > > >and included > >-Dht

RE: Tomcat 3.3 and 4.x tuning via command line

I don't know if the Eclipse configuration allows you to specify -D= in Tomcat's startup. If it does, I think a lot of this can be done in Tomcat 3.3.1 using parameter substitution. I have used in server.xml and included -Dhttp.port=8080 in the startup command to make server.xml runt

RE: Tomcat 3.3 - Cactus Issue

On Tue, 5 Feb 2002, Larry Isaacs wrote: > I tried adding a Thread.sleep(1) just before the call to > TcpConnection.shutdownInput() in Http10Interceptor. > A System.out.println() within shutdownInput's "while" > never prints during a successful Cactus run on Win2k. > Is there anything different I

RE: Tomcat 3.3 - Cactus Issue

riginal Message- From: Larry Isaacs Sent: Tue 2/5/2002 2:56 PM To: 'Tomcat Developers List' Cc: Subject: RE: Tomcat 3.3 - Cactus Issue > -Original Message- > From: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >[mailto:[EMAIL PROTECTED]] > Sent: Tuesd

RE: Tomcat 3.3 - Cactus Issue

> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 05, 2002 2:46 PM > To: Tomcat Developers List > Subject: RE: Tomcat 3.3 - Cactus Issue > > > On Tue, 5 Feb 2002, Larry Isaacs wrote: > > One question -

RE: Tomcat 3.3 - Cactus Issue

On Tue, 5 Feb 2002, Larry Isaacs wrote: > I looked for this and didn't find that there was any POST data > sent and none was read. I certainly could have missed something. > I don't completely understand everything that Cactus' controller > servlet does on the Tomcat side. However, I think I ch

RE: Tomcat 3.3 - Cactus Issue

Larry, See below. > -Original Message- > From: Larry Isaacs [mailto:[EMAIL PROTECTED]] > Sent: 05 February 2002 19:03 > To: 'Tomcat Developers List' > Subject: RE: Tomcat 3.3 - Cactus Issue > > Comments below. > [snip] > > > > Let

RE: Tomcat 3.3 - Cactus Issue

> Vincent: is your test servlet reading the body i.e. calls > getParameters() if it's a url-encoded body, or read > the full stream ? > > If not, I believe the current behavior is correct and shouldn't > be changed - it signals the CLIENT that whatever it posted > was not read, and that's a very

Re: Tomcat 3.3 - Cactus Issue

On Tue, 5 Feb 2002 [EMAIL PROTECTED] wrote: > Most of the time it happens when something is still in the write > buffer ( i.e. unsent or unread ), and the remote side is closing > the connection. I'll try again: Assuming CLIENT sending data to SERVER. The exception happens when: - server has r

RE: Tomcat 3.3 - Cactus Issue

Comments below. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 05, 2002 12:45 PM > To: Tomcat Developers List > Subject: Re: Tomcat 3.3 - Cactus Issue > > > Hi Larry, > > We had a similar problem lon

Re: Tomcat 3.3 - Cactus Issue

Hi Larry, We had a similar problem long time ago - with the POST and the extra CRLF. While investigating it, I found a lot of interesting stuff about "Connection reset by peer" :-) Most of the time it happens when something is still in the write buffer ( i.e. unsent or unread ), and the remote s

RE: Tomcat 3.3 getRemoteHost always returns "localHost" - Is there any 3.3 production version has patch applied

January 31, 2002 2:25 PM > To: Tomcat Users List > Subject: RE: Tomcat 3.3 getRemoteHost always returns "localHost" - Is > there any 3.3 production version has patch applied > > > Use the cvs version. Works perfectly fine in production > environments and is >

Re: Tomcat 3.3 deployment - last minute problem

Original Message - From: "Renato" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, December 18, 2001 6:27 PM Subject: Re: Tomcat 3.3 deployment - last minute problem > Hi all, > > I'm investigating this problem and may found

Re: Tomcat 3.3 deployment - last minute problem

ed are > src/facade22/org/apache/tomcat/facade/JspInterceptor.java and > src/share/org/apache/jasper/compiler/Compiler.java, if you want to dig > through the code. > - Original Message - > From: "Renato" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]>

Re: Tomcat 3.3 deployment - last minute problem

sper/compiler/Compiler.java, if you want to dig through the code. - Original Message - From: "Renato" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, December 18, 2001 6:27 PM Subject: Re: Tomcat 3.3 deployment - last minute

Re: Tomcat 3.3 deployment - last minute problem

Reply-to: "Tomcat Developers List" > From: "Renato" > Date: Fri Dec 14 15:19:28 2001 > To: "Tomcat Developers List" , > Tomcat Developers List , > , > Subject: Re: Tomcat 3.3 deployment - last minute problem > > Hi, > > This is what I'm u

Re: Tomcat 3.3 deployment - last minute problem

Hi, This is what I'm using: <%@ page contentType="text/html; charset=ISO-8859-1" %> I saw the servlet generated in the work directory and it actually write the response.setContentType("text/html;charset=ISO-8859-1") ( default type in server.xml is set to ISO-8859-1 too ) How can I know the

Re: Tomcat 3.3 deployment - last minute problem

On Fri, 14 Dec 2001, Renato wrote: > *** HTML pages with latin characters don't display correctly on Linux *** > > ( JSP file with: ) > Ex: áéíóú > > It's maybe a problem with the locale variables on my Linux, which I don't > quite understand ( tried LC_ALL, LANG, LC_CTYPE and it didn't work )

Re: Tomcat 3.3 (JDK 1.1 compatibility fixes)

Any news on this one James ? Do you have any patch that could add jar: support to SimpleClassLoader ? We could implement a workaround, but if possible I would fix this by supporing jar URLs where not available. Costin On Fri, 7 Sep 2001, James THOMAS wrote: > > I'm using IBM's JDK 1.1.8 > I

Re: Tomcat 3.3 (JDK 1.1 compatibility fixes)

I'm using IBM's JDK 1.1.8 I feel almost certain that it does not have a "jar" protocol handler. I tried your suggestion but I still get the exception: java.net.MalformedURLException: unknown protocol: jar at java.lang.Throwable.(Throwable.java:74) at java.lang.Exception.(Exceptio

Re: Tomcat 3.3 (JDK 1.1 compatibility fixes)

Thanks again James. I think I understand now. First question - what VM are you using ? JDK1.1.8 ( Sun and IBM ) seem to have handlers for jar protocol ( even if it's not standard AFAIK ). Long time ago I tested with kaffe and it worked - but I'm not sure I tested getResource(). The real problem

Re: Tomcat 3.3 (JDK 1.1 compatibility fixes)

Thanks for the great info Costin. Just an FYI, I did implement another solution, which was to implement a "Handler" class for the "jar" protocol. Interestingly enough, it was sufficient to only have a class that is responsible for the "jar" protocol. The implementation of the class could be cr

Re: Tomcat 3.3 (JDK 1.1 compatibility fixes)

Thanks James, I'm very happy to see your contributions. ( and my appologies for not testing with 1.1 often enough ). > >jakarta-tomcat-3.3-dev-src\src\share\org\apache\tomcat\util\depend\DependClassLoader.java > == > The method

RE: Tomcat 3.3 contextAdmin issues

On 20 Aug 2001 02:01:12 +0200, Paulo Gaspar wrote: > Your explanation sure helps understanding what functionality is intended > for each tag. I can take a look at that too. It is easier for me to > understand the taglibs than the rest of Tomcat. > =;o) Well, I hope understanding the rest of tom

RE: Tomcat 3.3 contextAdmin issues

Answer inline: > -Original Message- > From: Costin Manolache [mailto:[EMAIL PROTECTED]] > Sent: Saturday, August 18, 2001 8:29 PM > > On 18 Aug 2001 19:56:33 +0200, Paulo Gaspar wrote: > > ... > > > The first two things that are really confusing are: > > - the existence of 2 lines of

Re: Tomcat 3.3 contextAdmin issues

On 18 Aug 2001 19:56:33 +0200, Paulo Gaspar wrote: > I have been trying to improve a bit on the "admin" > application, especially on the "contextAdmin" bit, > tweaking its web pages/JSPs in order to add functionality > and ease of use. Great :-) > I am especially interested on making it easier

Re: tomcat 3.3 proposals cleanup - next step ?

On Tue, 26 Jun 2001, GOMEZ Henri wrote: > Larry does a cleanup on Tomcat 3.3 project > and remove many dirs in proposal but > > I removed all the proposal subdir from my > local CVS and got all the proposal subdir > trees at the next checkout. > In the Unix and CYGWIN versions of CVS

Re: Tomcat 3.3 or 4.0 under Netbeans 3.2 anyone?

Neeme, I didn't try myself, but the basic scheme for debugging servlets is the following: 1) Modify the Tomcat startup script so JVM runs in the debugging mode - we use something like the following: C:\jdk1.3.1\jre\..\bin\java -classic -Xdebug -Xnoagent -Xrunjdwp:transport=d t_socket,address=pj

RE: Tomcat 3.3 or 4.0 under Netbeans 3.2 anyone?

ok, nevermind, I already found some help for this: http://www.netbeans.org/www-nbusers/msg06837.html Neeme > -Original Message- > From: Neeme Praks [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, May 23, 2001 3:13 PM > To: [EMAIL PROTECTED] > Subject: Tomcat 3.3 or 4.0 under Netbeans 3.2

RE: Tomcat 3.3 Milestone 3 status

Larry, I just tested this with 3.2.2b5 using Apache, mod_jk and AJP12 and the ".jsp%20" problem does indeed exist. When running stand-alone the request returns a 404 error, but with mod_jk the JSP source is returned. If you could port your fix into tomcat_32 that would be great. Let me know wh

RE: Tomcat 3.3 Milestone 2 status

Hi, The jakarta-tomcat project has been tagged in CVS, so commits may resume. If you need Tomcat 3.3 Milestone 2 source, be sure to checkout with the tag tomcat_33_m2. I have built the Windows connectors for Milestone 2. Those who wish to contribute additional connectors may e-mail me directly.

RE: Tomcat 3.3 Milestone 1 Status

> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 09, 2001 2:05 PM > To: '[EMAIL PROTECTED]' > Subject: Re: Tomcat 3.3 Milestone 1 Status > > > Hi Larry, > > What about doing that after weekend ?

Re: Tomcat 3.3 Milestone 1 Status

Hi Larry, What about doing that after weekend ? Let's say is superstition, but so far Monday has been a good day for milestones. > Though not completely frozen, only simple (i.e. safe) bug fixes should > be made at this point. If there is something bigger that you think > should be in TC3.3m1

RE: Tomcat 3.3 Release Plan Voting Results

Hi Larry, I did not vote since I have no right to do it, but I would like to help. I am starting to use TC 3.x HEAD and getting familiar with its internals. If there are some fixes that do not demand for a wide knowledge of Tomcat (as if they just involve a couple of modules) I am willing to do

Re: Tomcat 3.3

Quoting "Pier P. Fumagalli" <[EMAIL PROTECTED]>: > "Craig R. McClanahan" wrote: > > > > For the record, Sun hired me in March, 2000, so that I could work on > Tomcat full > > time instead of it just being a hobby (as it was when the original > code was > > written). :-) > > And thank you for n

Re: Tomcat 3.3

Yeah i saw that. I'm planning a few updates. Jon Stevens wrote: > on 12/21/2000 1:13 PM, "Craig R. McClanahan" <[EMAIL PROTECTED]> > wrote: > > > updating the web site is yet another useful way to > > contribute). > > It is even documented on how to do that! > >

Re: Tomcat 3.3

on 12/21/2000 1:13 PM, "Craig R. McClanahan" <[EMAIL PROTECTED]> wrote: > updating the web site is yet another useful way to > contribute). It is even documented on how to do that! :-) -jon -- Honk if you love peace and quiet.

Re: Tomcat 3.3

Andy wrote: > > From your comments I have a question: Has 4.0 been voted on ? ( if this is > politically charged please read this in the context it is intended which is NOT > controversy, I'm a programmer not a political type)... Yes, Tomcat 4.0 as been voted on months ago and all -1s have be

Re: Tomcat 3.3

"Craig R. McClanahan" wrote: > > For the record, Sun hired me in March, 2000, so that I could work on Tomcat full > time instead of it just being a hobby (as it was when the original code was > written). :-) And thank you for not accepting my offer at that time, otherwise you would be working o

Re: Tomcat 3.3

Andy wrote: > > Maybe the best thing would be if one of the commiters gave me a piece of their > bug they don't feel like finding. > The interim bug reporting system we are using has tons of outstanding bugs. I would not bother with the Tomcat 3.1 bugs -- anyon

Re: Tomcat 3.3

"Craig R. McClanahan" wrote: > Andy wrote: > > > But, that being the case (and I know I'm touching on a sore spot) what will > > be the lifespan of 3.3. > > Since a proposal to publish a "Tomcat 3.3" has never been formally presented and > voted on, the only logically correct answer is "I don't k

Re: Tomcat 3.3

Andy wrote: > But, that being the case (and I know I'm touching on a sore spot) what will > be the lifespan of 3.3. Since a proposal to publish a "Tomcat 3.3" has never been formally presented and voted on, the only logically correct answer is "I don't know." Depending on the results of a vote,

Re: Tomcat 3.3

Hello, I've been reading both this and the dev list for about a month and asking/answering the more well put user questions (meaning I don't do to well on the ones that just say "Tomcat 3.x.x doesn't work on linux) and nothing else). I'd like to contribute to a tomcat, but since there are th

RE: Tomcat 3.3 / 4.0 confusion, rant and plan...

> Yes, We saw many reference of code to be fixed on 3.3. Now that some want to > > kill 3.3 and directly play with 4.0, the risk of having a 3.x branch > (the current branch) falling in 'unsupported software land' is VERY HIGH. This is open source - it's supported as long as some developers are

RE: Tomcat 3.3 / 4.0 confusion, rant and plan...

>I am working on the 3.x branch for about a year and made clear >many times >that I'll continue to work on it for a while. At least until it's the >fastest and most secure servlet container ( we are close, but >not there ). > >I see there is a lot of interest in killing 3.x and making it >"EOL"

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

> I think the Resources stuff are at the right spot in the architecture : > hidden behind the ServletContext, so that the data they abstract is > availible to any servlet. The Resource stuff is fine ( I would liked a JNDI Context more as an abstraction, but it's just my taste, I like Resource too

RE: Tomcat 3.3 / 4.0 confusion, rant and plan...

>> 1) Release Tomcat 3.2 final (soon, please!) > +1 It will help at least to reduce the questions on TOMCAT 3.1 which many users think the stable release. 2) Create a new proposal tree alongside with Catalina (new >name to avoid >>confusion, please) -1, yes it will be hard to follow 3 tre

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

> > - If it was possible to avoid code duplication for as many components as > > possible it would be great ;) Fixes / improvements are really hard to merge > > otherwise. Since I think the main point of disagreement is the servlet > > engine core, that should be doable. > > That's what I think to

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

> > Servlet2.0 -> Tocmat3.3 > > Servlet2.1 -> Tomcat3.3 > > Servlet2.2 -> Tomcat3.3 > > Servlet2.3 -> Tomcat3.3 > > Servlet.next -> Tomcat3.3 > > I don't agree. > Having : > Servlet2.0 -> TocmatNext > Servlet2.1 -> TomcatNext > Servlet2.2 -> TomcatNext > Servlet2.3 -> TomcatNext > Servlet.next ->

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

>> > - I start a new revolution in tomcat3.2 space ( proposals/something >> > ), and all the implementation of 2.3 and all controversial stuff >> > will go there ( i.e. all new features, like dav, http1.1, resource >> > caching, the new SMTP and POP3 protocols - since any feature will be >> > in f

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

> > - I start a new revolution in tomcat3.2 space ( proposals/something ), > > and all the implementation of 2.3 and all controversial stuff will go > > there ( i.e. all new features, like dav, http1.1, resource caching, the > > new SMTP and POP3 protocols - since any feature will be in fact just

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

[EMAIL PROTECTED] wrote: > What about this: > > - I start a new revolution in tomcat3.2 space ( proposals/something ), > and all the implementation of 2.3 and all controversial stuff will go > there ( i.e. all new features, like dav, http1.1, resource caching, the > new SMTP and POP3 protocols -

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

- Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, November 04, 2000 4:27 PM Subject: Re: Tomcat 3.3 / 4.0 confusion, rant and plan... > And why not: > > Servlet2.0 -> Tocmat3.3 > Servlet2.1 -> Tomcat3.3 > Ser

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

Pier P. Fumagalli wrote: > > If you want to go on and make a 3.3, do it, but if you want to > implement Servlet 2.3 in that release, you'll get my -1... Whether I personally agree with 3.x design or not, as an ASF member myself, I believe that it is important to protect Costin's right to pursue i

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

[EMAIL PROTECTED] wrote: > > What about this: > > - I start a new revolution in tomcat3.2 space ( proposals/something ), > and all the implementation of 2.3 and all controversial stuff will go > there ( i.e. all new features, like dav, http1.1, resource caching, the > new SMTP and POP3 protocols

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

"Pier P. Fumagalli" wrote: > > Hans Bergsten <[EMAIL PROTECTED]> wrote: > > > "Pier P. Fumagalli" wrote: > >> > >> Sorry for starting what it might end up as a long flamewar, but reading > >> almost 500 emails on the list I ended up a little confused... Also, in a > >> bunch of side discussions,

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

> Servlet 2.0? Apache JServ (Actually, we might end up moving it to Jakarta as > an "historic" piece of code when Java.Apache.ORG dies) > > Servlet 2.1? (fuck, we don't have it, any volunteer?) > > Servlet 2.2/JSP 1.1? Tomcat 3.x (3.2, 3.3, 3.4, 3.5 and so on, as long as >

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > What about this: > > - I start a new revolution in tomcat3.2 space ( proposals/something ), > and all the implementation of 2.3 and all controversial stuff will go > there ( i.e. all new features, like dav, http1.1, resource caching, the > new SMT

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

> Costin, would you consider bringing your brains into the 4.0 tree? > Is 3.3 that good that it should weigh in _against_ (as a competeing > implementation) 4.0? I think it is that good. Almost all the projects I am interested in doing requires a 3.3-like design ( and working on a servlet conta

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> time explaining to people, "Well, 3.x is sort of this unfinished thing that >> they weren't happy with, so they started 4.x". To me, that DOES give the > > 3.x and 4.x are 2 different servlet containers, with very different > design. The only conf

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

Hans Bergsten <[EMAIL PROTECTED]> wrote: > "Pier P. Fumagalli" wrote: >> >> Sorry for starting what it might end up as a long flamewar, but reading >> almost 500 emails on the list I ended up a little confused... Also, in a >> bunch of side discussions, but related always to the same topic, I fe

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

What about this: - I start a new revolution in tomcat3.2 space ( proposals/something ), and all the implementation of 2.3 and all controversial stuff will go there ( i.e. all new features, like dav, http1.1, resource caching, the new SMTP and POP3 protocols - since any feature will be in fact ju

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

The problem of the division of finite resources remains. Costin, would you consider bringing your brains into the 4.0 tree? Is 3.3 that good that it should weigh in _against_ (as a competeing implementation) 4.0? Pier, Craig, have you done all you can to get Costin "on-board" with 4.0? I just f

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

Michael Percy <[EMAIL PROTECTED]> wrote: > > Costin is an avid developer devoted to this project and technology, and you > are fools to lose him and fork the project. Costin is a great guy, I have nothing personal against him... I was so happy when he got his green card last week because I consid

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

Craig R. McClanahan wrote: > >> Are you saying what I hope you're saying, that you're stepping in >> as release manager for 3.2 to make sure it gets released quickly? > >I don't care who does the actual release (I will if Sam can't and >everyone else is OK with that), but I want to stop having to

RE: Tomcat 3.3 / 4.0 confusion, rant and plan...

Costin is an avid developer devoted to this project and technology, and you are fools to lose him and fork the project. I think it is possible that many contributors (present and potential future) will follow him. He is one of the few major contributors not employed by Sun. I don't see why there c

RE: Tomcat 3.3 / 4.0 confusion, rant and plan...

> So far it seems everyone is certain about how bad 3.3 is and how good 4.0 > is, and you may be right - but I do hope that you spent the required time > to understand both. What would benifit everyone the most is the fastest, most reliable, feature-rich (past the specs) container/jsp engine out

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

That's a very interesting discussion, I certainly learned a lot from it. So, tomcat3.3 is confusing and shouldn't be called tomcat because catalina is tomcat. And while tomcat3.2 was ok, and nobody complained that the performance increased several times and a lot of features were added, for tom

RE: Tomcat 3.3 / 4.0 confusion, rant and plan...

Everyone wants a TC3.2 -- I believe the only major concerns over the past couple weeks have been expressed in this snippet from a week ago: - snip - > It seemed that the last outstanding issue was the compilation under JDK > 1.1, but that should be fixed now. So is there still som

RE: Tomcat 3.3 / 4.0 confusion, rant and plan...

Some non-committer 2c here from me. Both of these things... >From Nick: > 1) The fact that there are smart software developers out there > contributing to Tomcat 3.x codebase and not necessarily contributing to > the 4.0 codebase is a failure of the Jakarta Apache community to obtain > sufficie

Re: Tomcat 3.3 / 4.0 confusion, rant and plan...

>> I believe development on the 3.x tree MUST continue, until Tomcat 3.x >> truly IS the RI of Servlet 2.2. Anything else would not make sense. >> The numbering (3.2, 3.3) does not matter. >> > > You will find that the 3.3 tree is pretty nearly as big an > architectural change (from 3.2) as is 4

  1   2   >