jaxp 1.0.1 and 1.1 RPMs
Hi, A quick note to say that both jaxp 1.0.1 and 1.1ea RPM are available. But could I make then available to http://rpmized.free.fr/ ? A licence problem may be ? Also could you see at the next 'Jakarta Project Management Committee' was to do with all the RPMs I've released ? I've done a proposition and some commiters were +1 to have such distro. Regards "Pour la plupart des hommes, se corriger consiste à changer de défauts." -- Voltaire
Re: VOTE: New Commiter Shai Fultheim (was:RE: Tomcat session replicator)
+1 Nacho wrote: Shai has contributed great bug fixes ( one specially difficult in 3.2, thanks Shai ) and he wants to contribute a distributed session manager It has been proposed as committer by Craig in a informal way, now it's proposed in a formal way :-) it has my +1 as well +1 from Craig in the message below. Votes , please. -- Glenn Nielsen [EMAIL PROTECTED] | /* Spelin donut madder| MOREnet System Programming | * if iz ina coment. | Missouri Research and Education Network | */ | --
ResponseImpl class -- finish()
Hi In the "finish()" method of ResposeImpl i wanted to know the significance of request.getContextManager().doAfterBody(request, this); the implementation of the doAfterBody(request, this) calls the AfterBody(request) returns the value of 0. so if we could avoid this then we could free the response object early.. thnx in advance... v i n a y
MUD: when to refactor or reconstruct?
Stein, Gee, I wonder if you suggested this piece because of the TC3.x vs TC4.x wars? :-) I wonder if there is any empirical criteria that can be appealed to in deciding which situation TC is in. Without it, the argument seems to go nowhere, since what is beautiful/functional/etc for one is ugly/dysfunctional/etc for another. Roy -- Roy Wilson E-mail: [EMAIL PROTECTED] Original Message On 12/22/00, 3:42:13 PM, "Stein M. Eliassen" [EMAIL PROTECTED] wrote regarding Re: Mud (Was: [OT] Holiday Reading - Refactoring): Hi, about mud, here is a pattern called "Big ball of mud" by Brian Foote and Joseph Yoder. Read it! http://www.laputan.org/mud/ Regards Stein M. Eliassen System Developer - KPNQwest Norway AS - Business communications @ the speed of light.
TOMCAT Architecture and Design Documents ?
Hi All, I want to understand the architecture and design of Tomcat. Are the architecure and design documents available for public. I will appreciate if someone can point me to the site where this information is available. thanks Shahid
BugRat Report #662 has been filed.
Bug report #662 has just been filed. You can view the report at the following URL: http://znutar.cortexity.com/BugRatViewer/ShowReport/662 REPORT #662 Details. Project: Tomcat Category: Feature Requests SubCategory: Enhancement Class: docbug State: received Priority: high Severity: critical Confidence: public Environment: Release: 3.1.1 JVM Release: 1.3 Operating System: Win32 OS Release: 98 Platform: Windows 98 Synopsis: bug in tomcat.bat Description: remove this line from tomcat.bat: echo tomcat (start^|run^|env^|stop) startup will work correctly now Title: BugRat Report # 662 BugRat Report # 662 Project: Tomcat Release: 3.1.1 Category: Feature Requests SubCategory: Enhancement Class: docbug State: received Priority: high Severity: critical Confidence: public Submitter: Larry Wilberton ([EMAIL PROTECTED]) Date Submitted: Dec 23 2000, 11:43:25 CST Responsible: Z_Tomcat Alias ([EMAIL PROTECTED]) Synopsis: bug in tomcat.bat Environment: (jvm, os, osrel, platform) 1.3, Win32, 98, Windows 98 Additional Environment Description: Report Description: remove this line from tomcat.bat: echo tomcat (start^|run^|env^|stop) startup will work correctly now View this report online...
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core LocalStrings.properties StandardContext.java
craigmcc00/12/23 11:00:34
Modified:catalina/src/share/org/apache/catalina/core
LocalStrings.properties StandardContext.java
Log:
Add a backwards compatibility hack to the way that web application
deployment descriptors are parsed.
Tomcat 3.x accepted url-pattern arguments (inside a servlet-mapping or
a security-constraint) that did not conform to the syntax requirements
of the Servlet 2.2 specification, because it would explicitly add a
leading slash if it was omitted. Now, Tomcat 4.0 will accept such a
pattern, with a warning message to the log, *only* on applications that
declare themselves to use the Servlet 2.2 DTD.
For a 2.3 web app, Tomcat 4.0 enforces the syntax rules on url-pattern
arguments, which are spelled out explicitly in the spec.
Revision ChangesPath
1.22 +1 -0
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/LocalStrings.properties
Index: LocalStrings.properties
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/LocalStrings.properties,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- LocalStrings.properties 2000/12/14 02:56:14 1.21
+++ LocalStrings.properties 2000/12/23 19:00:31 1.22
@@ -60,6 +60,7 @@
standardContext.stoppingLoader=Exception stopping Loader
standardContext.stoppingManager=Exception stopping Manager
standardContext.stoppingWrapper=Exception stopping Wrapper for servlet {0}
+standardContext.urlPattern.patternWarning=WARNING: URL pattern {0} must start with
a '/' in Servlet 2.3
standardContext.wrapper.error=JSP file {0} must start with a '/'
standardContext.wrapper.warning=WARNING: JSP file {0} must start with a '/' in
Servlet 2.3
standardContext.invalidEnvEntryValue={0} environment entry has an invalid value for
specified type
1.33 +31 -5
jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java
Index: StandardContext.java
===
RCS file:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- StandardContext.java 2000/12/08 07:17:52 1.32
+++ StandardContext.java 2000/12/23 19:00:32 1.33
@@ -1,7 +1,7 @@
/*
- * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
1.32 2000/12/08 07:17:52 pier Exp $
- * $Revision: 1.32 $
- * $Date: 2000/12/08 07:17:52 $
+ * $Header:
/home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/StandardContext.java,v
1.33 2000/12/23 19:00:32 craigmcc Exp $
+ * $Revision: 1.33 $
+ * $Date: 2000/12/23 19:00:32 $
*
*
*
@@ -133,7 +133,7 @@
*
* @author Craig R. McClanahan
* @author Remy Maucherat
- * @version $Revision: 1.32 $ $Date: 2000/12/08 07:17:52 $
+ * @version $Revision: 1.33 $ $Date: 2000/12/23 19:00:32 $
*/
public class StandardContext
@@ -1039,6 +1039,7 @@
for (int i = 0; i collections.length; i++) {
String patterns[] = collections[i].findPatterns();
for (int j = 0; j patterns.length; j++) {
+patterns[j] = adjustURLPattern(patterns[j]);
if (!validateURLPattern(patterns[j]))
throw new IllegalArgumentException
(sm.getString
@@ -1187,6 +1188,8 @@
if ((servletName != null) (urlPattern != null))
throw new IllegalArgumentException
(sm.getString("standardContext.filterMap.either"));
+// Because filter-pattern is new in 2.3, no need to adjust
+// for 2.2 backwards compatibility
if ((urlPattern != null) !validateURLPattern(urlPattern))
throw new IllegalArgumentException
(sm.getString("standardContext.filterMap.pattern",
@@ -1353,7 +1356,7 @@
if (findChild(name) == null)
throw new IllegalArgumentException
(sm.getString("standardContext.servletMap.name", name));
-pattern = RequestUtil.URLDecode(pattern);
+pattern = adjustURLPattern(RequestUtil.URLDecode(pattern));
if (!validateURLPattern(pattern))
throw new IllegalArgumentException
(sm.getString("standardContext.servletMap.pattern", pattern));
@@ -3054,6 +3057,29 @@
protected void addDefaultMapper(String mapperClass) {
super.addDefaultMapper(this.mapperClass);
+
+}
+
+
+/**
+ * Adjust the URL pattern to begin with a leading slash, if appropriate
+ * (i.e. we are
cvs commit: jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/test HttpConnector.java HttpProcessor.java
craigmcc00/12/23 11:39:55 Modified:catalina/src/share/org/apache/catalina/connector/http HttpConnector.java HttpProcessor.java catalina/src/share/org/apache/catalina/connector/test HttpConnector.java HttpProcessor.java Log: Use individual thread synchronization objects for each instance of HttpConnector and HttpProcessor. Submitted by: Luc Vanlergerghe [EMAIL PROTECTED] Revision ChangesPath 1.6 +5 -5 jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/http/HttpConnector.java Index: HttpConnector.java === RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/http/HttpConnector.java,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- HttpConnector.java2000/12/16 19:01:23 1.5 +++ HttpConnector.java2000/12/23 19:39:54 1.6 @@ -1,7 +1,7 @@ /* - * $Header: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/http/HttpConnector.java,v 1.5 2000/12/16 19:01:23 remm Exp $ - * $Revision: 1.5 $ - * $Date: 2000/12/16 19:01:23 $ + * $Header: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/http/HttpConnector.java,v 1.6 2000/12/23 19:39:54 craigmcc Exp $ + * $Revision: 1.6 $ + * $Date: 2000/12/23 19:39:54 $ * * * @@ -94,7 +94,7 @@ * * @author Craig R. McClanahan * @author Remy Maucherat - * @version $Revision: 1.5 $ $Date: 2000/12/16 19:01:23 $ + * @version $Revision: 1.6 $ $Date: 2000/12/23 19:39:54 $ */ @@ -253,7 +253,7 @@ /** * The thread synchronization object. */ -private String threadSync = ""; +private Object threadSync = new Object(); /** 1.19 +5 -5 jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/http/HttpProcessor.java Index: HttpProcessor.java === RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/http/HttpProcessor.java,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- HttpProcessor.java2000/12/17 01:05:40 1.18 +++ HttpProcessor.java2000/12/23 19:39:54 1.19 @@ -1,7 +1,7 @@ /* - * $Header: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/http/HttpProcessor.java,v 1.18 2000/12/17 01:05:40 craigmcc Exp $ - * $Revision: 1.18 $ - * $Date: 2000/12/17 01:05:40 $ + * $Header: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/http/HttpProcessor.java,v 1.19 2000/12/23 19:39:54 craigmcc Exp $ + * $Revision: 1.19 $ + * $Date: 2000/12/23 19:39:54 $ * * * @@ -107,7 +107,7 @@ * * @author Craig R. McClanahan * @author Remy Maucherat - * @version $Revision: 1.18 $ $Date: 2000/12/17 01:05:40 $ + * @version $Revision: 1.19 $ $Date: 2000/12/23 19:39:54 $ */ final class HttpProcessor @@ -242,7 +242,7 @@ /** * The thread synchronization object. */ -private String threadSync = ""; +private Object threadSync = new Object(); /** 1.4 +5 -5 jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/test/HttpConnector.java Index: HttpConnector.java === RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/test/HttpConnector.java,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- HttpConnector.java2000/09/08 22:29:35 1.3 +++ HttpConnector.java2000/12/23 19:39:55 1.4 @@ -1,7 +1,7 @@ /* - * $Header: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/test/HttpConnector.java,v 1.3 2000/09/08 22:29:35 craigmcc Exp $ - * $Revision: 1.3 $ - * $Date: 2000/09/08 22:29:35 $ + * $Header: /home/cvs/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/connector/test/HttpConnector.java,v 1.4 2000/12/23 19:39:55 craigmcc Exp $ + * $Revision: 1.4 $ + * $Date: 2000/12/23 19:39:55 $ * * * @@ -93,7 +93,7 @@ * purposes. Not intended to be the final solution. * * @author Craig R. McClanahan - * @version $Revision: 1.3 $ $Date: 2000/09/08 22:29:35 $ + * @version $Revision: 1.4 $ $Date: 2000/12/23 19:39:55 $ */ @@ -245,7 +245,7 @@ /** * The thread synchronization object. */ -private String threadSync = ""; +
cvs commit: jakarta-tomcat-4.0/catalina build.xml
craigmcc00/12/23 12:05:19
Modified:catalina build.xml
Log:
Modify the Catalina build script to pick up the current version of the
regular expression library.
(Yes, we still need to remodel the build scripts to take advantage of Ant
1.2's ability to create classpaths for you).
Revision ChangesPath
1.28 +1 -1 jakarta-tomcat-4.0/catalina/build.xml
Index: build.xml
===
RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/build.xml,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- build.xml 2000/12/11 03:12:30 1.27
+++ build.xml 2000/12/23 20:05:19 1.28
@@ -17,7 +17,7 @@
property name="jnet.jar"value="${jsse.home}/lib/jnet.jar"/
property name="jsse.jar"value="${jsse.home}/lib/jsse.jar"/
property name="jmxri.jar" value="${jmx.home}/lib/jmxri.jar"/
- property name="regexp.jar" value="${regexp.home}/jakarta-regexp-1.1.jar"/
+ property name="regexp.jar" value="${regexp.home}/jakarta-regexp-1.2.jar"/
property name="servlet.jar" value="${servletapi.home}/lib/servlet.jar"/
!-- === BUILD: Create Directories == --
BugRat Report #613 was closed (apparently by: Craig R. McClanahan)
Report #613 was closed by Person #0 Synopsis: lossing connection on POST (logged in as: Craig R. McClanahan)
cvs commit: jakarta-tomcat-4.0/webapps/examples/WEB-INF web.xml
craigmcc00/12/23 12:36:27 Modified:webapps/examples/WEB-INF web.xml Log: Remove unneeded extension mapping. Revision ChangesPath 1.9 +0 -8 jakarta-tomcat-4.0/webapps/examples/WEB-INF/web.xml Index: web.xml === RCS file: /home/cvs/jakarta-tomcat-4.0/webapps/examples/WEB-INF/web.xml,v retrieving revision 1.8 retrieving revision 1.9 diff -u -r1.8 -r1.9 --- web.xml 2000/11/02 06:16:49 1.8 +++ web.xml 2000/12/23 20:36:26 1.9 @@ -85,14 +85,6 @@ /servlet-mapping servlet-mapping servlet-name -snoop -/servlet-name -url-pattern -*.snp -/url-pattern -/servlet-mapping -servlet-mapping -servlet-name servletToJsp /servlet-name url-pattern
RE: [MY_OPINION] Tomcat 3.x
Hi people, I just came back from holidays and red all this thread at once. The main joke is in the initial posting where Jon goes from telling Costin that "It really scares me that you are the only person..." in its beginning to "We just don't have enough overall developer resources to support two different forks". I red it and I thought that Jon was trying to recruit Costin (the "only" TC3.3 man) to TC4.x because Jakarta had not enough developer resources to afford "wasting" Costin on 3.3 (only Costin since Jon says he is alone). Man... this got me confused: I thought Sun had a bunch of people working full time on Tomcat and then I learn that Jon is concerned about wasting ONE part-timer's work with 3.3!!! (Remember again that Jon says that Costin is the ONLY person interested in 3.3.) =:o) I am glad that further postings confirmed that there is a bunch of full time developers working on 4.x and that there is a lot of other people interested and working on 3.3. I am glad because: - Tomcat 4 is a very interesting evolution; - I can not afford to hold my breath until 4.x gets stable and I hope that 3.3 "gets there" soon(er) enough to provide me with a good production Servlet engine that supports JSPs. I would like to see a finished production Tomcat server soon. However, there is NO Tomcat version yet that provides all the functionality and robustness that most serious developers expect from a Servlet engine. The fact that production experience is being injected in Tomcat 3.3 is a reassurance to me that such a version will happen soon enough. Forcing the people that are doing that work in 3.3 to quit from 3.3 and learn 4.x is not the shortest path (in time) to use their knowledge in having _some_ Tomcat version REALLY production ready. I will believe that 4.x is production ready when it happens. The time-to-become-stable estimation is one of those that fails more often and by larger amounts. In the meantime, 3.3 looks closer. Refactoring is different from such a large redesign/rewrite as Tomcat 4.x is - and this holds true even if you call it Catalina or JServ 2. Lets see: - There are to many new ingredients, too many new components and too many new developers in Tomcat 4. Too many things can fail; - OTOH, in 3.3 there is Costin and 3.x-experienced guys cleaning up, refactoring and fixing what they know well, only adding new stuff where essential. Agin: - On one hand I see a lot of new pieces on 4.x that can provide a lot of unforeseen issues. - And OTOH I see work over a better known base with much less new pieces on 3.3. So, I have to believe that 3.3 is the shortest path to have some production ready Tomcat. I respect Craig a lot. A LOT really. But his judgment might be a bit biased since 4.x is his child. It is so easy to be (over)optimistic about the time-to-production of one's own child! I just don't know what to think about Jon. Maybe he got overexcited about 4.x new features and he wants to have it ready ASAP. Maybe that is why he makes this kind of political move with such enthusiasm that he even becomes incoherent. My political move is to defend 3.3, since I only get overexcited by having a Production Quality Tomcat AsSoonAsPossible! Yes, I like the future in Tomcat 4.x, but I need a PRESENT really soon too and 3.3 would be good enough for that. I will be clear - if Costin is forced to move away I will try to use anything that him and the other 3.3 guys post on SourceForge, on any other site or mail me privately. BUT if that happens I will be much less motivated to come back to Tomcat since Tomcat would have become a feud where there is no longer room for the competition and complementarities of good ideas. Remember that Tomcat 4.x wouldn't exist so soon if the argument against dividing resources would be applied with the focus on getting a production quality 3.x server out. And one could argue that such focus would better fulfill the responsibilities of the project towards its users. In the end, I think we are better with this division of resources and interests since it ensures that products get fully matured (as 3.3 for the 3.x line) while future more sophisticated designs evolve (4.x). Have fun, Paulo Gaspar -Original Message- From: Jon Stevens [mailto:[EMAIL PROTECTED]] Costin, It really scares me that you are the only person (as far as I can tell) that is seriously interested in maintaining and developing Tomcat 3.x into the future. It is not good to have the entire rest of the core developers work on Tomcat 4.x and having you sit here and say that you are going to work towards back porting everything that the Tomcat 4.x people come up with on your own. Talk about a complete duplication of effort by only a single individual. We just don't have enough overall developer resources to support two different forks of the same project going on at the same time! This isn't good! :-( thanks, -jon
[PATCH} Re: Tomcat 3.2.1 bug if not root-context defined.
I have attached a patch that corrects this problem for me.
Please try it out and see if it works for you so that a committer can
apply it.
This is a patch against the current 3.2 branch for the ContextManager.
Happy Holidays!
Shawn
Klaus Friedel wrote:
Tomcat 3.2.1 fails to deliver a resource, if no root-context is defined in
serverl.xml.
If you do not define the root-context "" in server.xml and request a non-existing
resource,
Tomcat will loop forever in PrefixMapper.getLongestPrefixMatch() trying to find a
Container for "".
Bye,
Klaus.
--
Shawn McMurdo mailto:[EMAIL PROTECTED]
Lutris Technologieshttp://www.lutris.com
Enhydra.Orghttp://www.enhydra.org
Title: Not found!
Index: ContextManager.java
===
RCS file: /home/cvspublic/jakarta-tomcat/src/share/org/apache/tomcat/core/ContextManager.java,v
retrieving revision 1.100.2.19
diff -c -r1.100.2.19 ContextManager.java
*** ContextManager.java 2000/11/16 18:25:21 1.100.2.19
--- ContextManager.java 2000/12/24 01:57:28
***
*** 1015,1020
--- 1015,1043
Context ctx = req.getContext();
if(ctx==null) ctx=getContext("");
+ // XXX We handle this case specially
+ if (ctx == null) {
+ try {
+ res.setContentType("text/html");
+ String body = "Not found!";
+ res.setContentLength(body.length());
+ if (res.isUsingStream()) {
+ ServletOutputStream out = res.getOutputStream();
+ out.print(body);
+ out.flush();
+ } else {
+ PrintWriter out = res.getWriter();
+ out.print(body);
+ out.flush();
+ }
+ return;
+ } catch (IOException ioe) {
+ // XXX ignore, we tried
+ //ioe.printStackTrace();
+ return;
+ }
+ }
+
// don't log normal cases ( redirect and need_auth ), they are not
// error
// XXX this log was intended to debug the status code generation.
BugRat Report #624 was closed (apparently by: Nick Bauman)
Report #624 was closed by Person #0 Synopsis: Error 500 is returned (logged in as: Nick Bauman)
[BUG TRACKING] -- Bogus reports: let's get 'em closed before 2001
Hello Jakarta Horde, There are A LOT of bug reports in the Jakarta Bug Tracking system, many of them are not bugs, but in fact user and programmer errors cleverly disguised as bugs. (This is similar to the way I am not an actual programmer, but instead a strategically shaved chimpanzee! No, really!) Please let me know if you have ever filed a report from what you thought was a bug that turned out to be something tedious that you overlooked. Give me the bug report ID of the report you filed. If you can't remember the ID, give me as much information as you can and I can look it up without killing the database. Thanks, -Nick -- Nicolaus Bauman Software Engineer (member, ASPCA, since 1976)
RE: An open letter to 3 developers
-Original Message- From: Jon Stevens [mailto:[EMAIL PROTECTED]] on 12/19/2000 1:31 PM, "[EMAIL PROTECTED]" [EMAIL PROTECTED] wrote: And given that you didn't like what he said, you felt an urge to verify if he complies with the apache license ? No, that is how you decided to interpret it. But whatever. Costin interpretation was the obvious one to me too. It's not that often that I see apache people going after users - and definitely not on public mailing lists. I'm not "going after" anyone. I'm asking to see proof that he is following the license. I do that all the time when I see that people are using ASF software. Sure. I'm not sure why suddenly asking for proof license compliance is illegal or even immoral. -jon And "politeness"? Does that ring a bell? Paulo Gaspar
RE: An open letter to 3 developers
Brilliant! I would never be able to put it so well. I think that every word here is important and I subscribe them all. (Yes, that is why I didn't edit them.) Have fun, Paulo Gaspar -Original Message- From: Christopher Cain [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 19, 2000 09:44 Preamble: First off, let me take this opportunity to thank each and every one of you who has contributed to making Tomcat the great product that it is. I know that gets said sometimes, but not nearly enough. I have been a longtime lurker and occasional poster to this list. As a Java developer who has just recently begun poking around in the source code, I am not yet qualified to make any technical comments on Tomcat whatsoever, although I will be soon enough. I am also torn on the current disagreement that has apparently led to Costin's departure, as I think that both sides have some valid points. In short, I am in no position to offer answers or opinions. So instead, I feel like weighing in with my genuine feelings about losing such a fervent and talented developer as Costin. So like a child acting out during a rather messy parental divorce, here's my shot from the middle. (Please forgive the length of this, but hey, the subject did say "letter," so you were free to ignore it if you had actually felt like doing some real work.) Costin: You have my deepest thanks for the sheer volume of work you contributed to the product that runs every one of the applications I write for my customers. As a professional developer, I just want to add my voice to the countless other end users of the tomcat product who have posted here in thanks for your attention to the as-yet only major release of the product. From those of us on the outside looking in, who aren't really involved in +1's and PMC's and "revolutions," your efforts are appreciated tremendously. Your steadfast desire to see the 3.x product finished as you had envisioned it speaks to every self-respecting developer. You are underappreciated by some of those fellow developers IMHO, but your users thank you. And in the end, isn't that who are you writing the code for anyway? I think more people than you probably realize have much love, bro. Craig: You have always struck me as a fair and thoughtful project lead. I admire your ability to put your own political beliefs aside for the good of the project, as was evident when you switched from Catalina to work full-time on 3.2 bugfixes. Tomcat 3.2 was a better product for it, and we users owe you many thanks as well. In fact, as a servlet coder from back in the early days of Apache JServ, I owe you a great deal of thanks for your longstanding work in the field. As I said, I have no value judgement for 3.x vs. 4.x, but in the end I understand why a parting of the ways was probably inevitable. If I might take slight exception with some of your recent comments, however (hey, you knew it was coming, right :-) ... But, prospective "3.3" users should also be aware ... this time, if it ever did get released, I'm not going to be there to clean up Costin's bugs (as I had to do on both 3.1 and 3.2). I've got better things to do. This is precisely the kind of accusatory attitude and low-civility discourse that a) is about to get Jon a tounge-lashing below, and b) gives me pause about getting involved with this project at the moment. You two are (were) arguably the biggest contributors, are usually quite pleasant, and have respected each other for over a year! You realize that since both of you are my role models, this kind of talk will probably stunt my emotional development or something. Oh well, like they say, when the gods fight, it's always the little people that get stepped on. By the way, Tomcat 4.0 will be the web container in the next release of the Java2 Enterprise Edition (J2EE) reference implementation. As such, it is receiving the benefit of extensive testing within Sun, in addition to all the testing done by the open source community. On a serious note, that offends my open source sensibilities. I can appreciate your point about the additional testing, but I think the open source community by itself has ample testers, and "official sponsorship" as an argument always makes me a little uncomfortable. Anyway, just my $0.02 on that. Jon: You seem to irritate virtually every developer you bump into, including myself. For some reason there is always at least one of your kind on every dev list I subscribe to. You do not make your points respectfully, and as a result your points are usually lost in your demeanor. You see, I don't know whether your ideas are right or wrong, but when you phrase you answers in the form of pure acid, I just can't bring myself to care. In a previous post, which I apologize for not being able to locate in the archives and therefore quote directly, you allude to playing the bad
RE: future questions
Another overwhelming diplomacy lesson... I guess. Have fun, Paulo Gaspar -Original Message- From: Jon Stevens [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 20, 2000 01:21 To: tomcat-dev Subject: future questions Lets see how many of these questions come up in the future by users: I downloaded the latest J2EE and it includes Tomcat. However, when I looked on your website, it says that you have two versions of Tomcat. Which one comes with J2EE? Which one should I be using? I found a bug in 3.3. When is the next release going to happen? (Implying that we are going to have to continue on putting effort towards more 3.3.x releases.) I found a *serious* architectural issue in 3.3 that warrants a 3.4 release. What should we do now? (Implying that we are going to have to continue on putting effort towards more 3.3.x releases.) I looked at your website and there are two versions of Tomcat, which one should I use? They both seem to be in active development. Why is one better than the other? p.s. Costin, I had a great idea. I'm going to forward to you all of the personal email based Tomcat support questions that I get. Have fun answering them. :-) -jon
RE: Fuck It.
Sorry Pier, but I find it very lame to use history against reason. I do not see how your long personal history in Apache and all the epic remarks you make about it translate into a reason for your vote. You are talking like an old politician and not like an Open Source developer. Have fun, Paulo Gaspar -Original Message- From: Pier P. Fumagalli [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 21, 2000 12:38 To: [EMAIL PROTECTED] Subject: Re: Fuck It. Jon Stevens [EMAIL PROTECTED] wrote: To: Costin and the rest of you who commented. You obviously know what is best and have shown me that I simply have my head up my ass and I'm just a complete jerk and I should stop now and just let you do whatever you want. I give up. All of my previous -1 votes are now +1. Have fun. It's sad, my friend, to see you giving up like this. We've traveled a long way together, from my very first steps in open-source land in January 1998, to our marvelous meeting at the first ApacheCON in October 1998, the Jakarta room meeting, all JavaONEs, and all we did together to bring this project where it is right now. .. So, here I stand, my vote is a big -1 on a 3.3 as a newly architected servlet container, +1 on fixing bugs on 3.2 (actually 3.2.1 since Craig excellently pulled out all those security issues), +1 on improving performances on 3.2.1 (and I don't care if it's going to be called 3.2.2, 3.3 or 3.9, fuck release numbers on 3.x) and a big +1 on Catalina as the base servlet container for 4.0 no matter what this is our future, whether you like it or not. All other containers, please wait for a 5.0. And for once, so, my votes are in disagreement with you, Jon... :) As one of the people behind the scenes since before each of you got here, I believe my vote counts, and now, please prove me wrong. Pier -- Pier Fumagalli http://www.betaversion.org/ mailto:[EMAIL PROTECTED]
RE: Fuck It.
-Original Message- From: Pier P. Fumagalli [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 21, 2000 21:18 Thanks Rob. You EXACTLY hit the point... When we started the Jakarta project, what happened to JServ? NOTHING, it's still there, kicking asses since two years with no maintainers because Tomcat was the way to go... We developers got it, understood it, and carried on with our decisions, even if to someone that was a wrong one. No maintainers for 2 years? Are you sure? And what happened? Of course Craig felt left out in that, he was writing JServ 2.0, but he said "yes" to Jakarta, and because of that, he simply dropped the old container, until he came along and made the Catalina proposal... And now that's the way to go, that's what we decided, that's what I want to see happen. Pier sarcasm Of course! Let's go on with this Servlet Engine research project trying to find the Holly Graal of Servlet Engines. Costin is wasting our resources promoting the heretic idea of providing a (argh!) production (urgh!) quality version to Tomcat potential users. This is a very dangerous idea because users with a production level tool are not so helpful on helping us testing if the Holly Graal of Servlet Engines was achieved or not!!! This is the most dangerous part of this resource division! Of course that they must be kept unaware of this being a pure research project in order to keep being useful for our testing purposes. They must be keep the illusion that a production version is just around the corner! /sarcasm Have fun, Paulo Gaspar
RE: Fuck It.
-Original Message- From: Pier P. Fumagalli [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 21, 2000 22:17 Nacho wrote: I believe that architecture of 3.3 is right one. And you're free to believe what you want. As I am... Why we are not talking about that ? Because we already did, we closed that discussions months ago when the first 4.0 proposal came out and was voted upon. Where was your -1 when the decision was made? Sorry, but you're too late now. There will be a version 5 some day. Paulo
RE: Fuck It.
Cool down Gomez. You are being too dramatic. (Just like a French movie character! (o;= ) You must remember how Italian Pier can get and how he can then get lost in his epic tales. (Just like an outspoken and lame Italian movie character.) =:o) BTW: FYI in preparing further national jokes, I am Portuguese. Have fun, Paulo Gaspar -Original Message- From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 21, 2000 16:49 It's more a question than a request. I was really sad with Pier reaction. I really don't want to appear as a someone disturbing the Tomcat Project. As many others today, I wonder about the future of OpenSource and projects independance when corporations like IBM and Sun put (or hire) so many of the core developpers.
RE: F....
Agreed! Let Costin and the others make their job and then let code talk. Have fun, Paulo Gaspar -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, December 22, 2000 12:55 To: [EMAIL PROTECTED] Subject: Re: F 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 on reusable code... whatever, it's Xmas, go to the pub.
RE: F....
-Original Message- From: Jon Stevens [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 21, 2000 23:26 Tomcat 3.2 has *only* happened because Tomcat 4.0 wasn't ready. And I wonder when is it going to be. That is why I want the 3.3 alternative. Remember the history of Tomcat 4.0 and the fact that if Sun didn't donate a bunch of cruft software, we would have spent the time working on JServ 2.0 which is now what Tomcat 4.0 is. The fact of the matter is that because we had to deal with 3.x and support improving it that delayed the development of 4.0 to not being ready until now. So, a wrong decision was taken accepting Tomcat 3 instead of JServ 2??? Wrong decisions are possible at Tomcat then. So, why are you deffending voted decisions as the "irrefutable true path"? Have fun, Paulo Gaspar
