Re: [VOTE] Release Plan for Apache Tomcat 4.1
Remy Maucherat wrote: Remy Maucherat wrote: The goal of the Apache Tomcat 4.1 final release is to provide a stable container that supports 100% of the mandatory requirements of the Servlet 2.3 and JSP 1.2 specifications, as well as to improve and add many useful additional features on top of the existing Apache Tomcat 4.0 releases. And what do we do with 4.0? I still have problems with resources and lifecycles there and no enough time to fix them. I plan to propose releasing a 4.0.4 Beta 3 after a few bugfixes are merged (the one for bug 8092, mainly; probably also a few others, like 7575 and 6662 Hi Remy, this is good to hear, do you have any more specific plans and suggested dates for 4.0.4 Final ? Thanks Petr Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
Remy Maucherat wrote: Here is what Craig stated regarding context start/stop events: - - reload Reloads Context if it is a directory, does not reload if it is running from a war file. A reload does not reload the web applications web.xml. So if you make configuration changes to the web.xml file you need to do a stop/start. I'm not sure that stop/start actually does the right thing currently (haven't ever looked at that scenario), because it doesn't remove anything that was configured by the old web.xml file. - Thanks, I had forgotten about it :-( The start/stop order is cleaned up, but stop should probably clean more than it currently does. Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Request for more events to the LifeCycle Re: [VOTE] Release Plan for Apache Tomcat 4.1
I've not accessed the latest Catalina source since 4.0.1, and I can't access this from where I'm working now. I've written a small server that makes use of catalina parts, and as I wrote this server, I wished that LifeCycle had 4 events instead of 2 (Starting, started, stopping, stopped). This lets one keep better track of what's going on. I'd wanted to post this request to Bugzilla today, but there's some problem with accessing that site. Thanks, Sriram Sriram __ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Fwd: Request for more events to the LifeCycle Re: [VOTE] Release Plan for Apache Tomcat 4.1
Sorry, I hit the Send button accidently... Here's what I wanted to say: I've not accessed the Tomcat source since 4.0.1, and can't access it from where I'm working right now. I've used Tomcat 4 parts within a small server that I've written. I've also written a UI in Swing that listens to LifeCycle Events. I have the following questions : 1. Is it possible to have events such as starting, started, stopping, and stopped instead of the current two : starting and stopping ? 2. Are there any plans to include these events in future ? 3. Was there ever such an idea and was it voted against for some reason ? I was unable to access bugzilla, and therefore resorted to posting this request to the DEV list. Thanks, Sriram --- Sriram N [EMAIL PROTECTED] wrote: Reply-to: Tomcat Developers List [EMAIL PROTECTED] Date: Thu, 25 Apr 2002 08:02:46 -0700 (PDT) From: Sriram N [EMAIL PROTECTED] Subject: Request for more events to the LifeCycle Re: [VOTE] Release Plan for Apache Tomcat 4.1 To: Tomcat Developers List [EMAIL PROTECTED] I've not accessed the latest Catalina source since 4.0.1, and I can't access this from where I'm working now. I've written a small server that makes use of catalina parts, and as I wrote this server, I wished that LifeCycle had 4 events instead of 2 (Starting, started, stopping, stopped). This lets one keep better track of what's going on. I'd wanted to post this request to Bugzilla today, but there's some problem with accessing that site. Thanks, Sriram Sriram __ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] __ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/ -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
ballot [ ] +1 I approve this plan, and will help [X] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: /ballot -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
Remy Maucherat [EMAIL PROTECTED] wrote: [ ] +1 I approve this plan, and will help [X] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: Don't care about the new features of the container... The only thing I'm concerned about ATM are JSPs and those need to go on 4.0 as well... :) Pier -- I think that it's extremely foolish to name a server after the current U.S. President. B.W. Fitzpatrick -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
[X] +1 I approve this plan, and will help [ ] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: I will try and get the NetWare plugins for the JK2 stuff built and posted. Mike Anderson -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
On Wed, 24 Apr 2002, Remy Maucherat wrote: I'd like to call for a vote on the Apache Tomcat 4.1 Release Plan. The vote will run until 04/26, and will be followed, if the Release Plan is accepted, by a vote for the release of Apache Tomcat 4.1 Beta 1. ballot [X] +1 I approve this plan, and will help [ ] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
Remy Maucherat wrote: I'd like to call for a vote on the Apache Tomcat 4.1 Release Plan. The vote will run until 04/26, and will be followed, if the Release Plan is accepted, by a vote for the release of Apache Tomcat 4.1 Beta 1. ballot [ ] +1 I approve this plan, and will help [ ] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: /ballot Remy Release Plan for Apache Tomcat 4.1 == Introduction: This document is a release plan for the *final* release of Apache Tomcat 4.1. The goal of the Apache Tomcat 4.1 final release is to provide a stable container that supports 100% of the mandatory requirements of the Servlet 2.3 and JSP 1.2 specifications, as well as to improve and add many useful additional features on top of the existing Apache Tomcat 4.0 releases. And what do we do with 4.0? I still have problems with resources and lifecycles there and no enough time to fix them. Apache Tomcat 4.1 includes the following major new features over Apache Tomcat 4.0: * JMX based administration features * JSP and Struts based administration web application * New Coyote HTTP/1.1 connector * New Coyote JK2 AJP 1.4 connector * Rewritten Jasper JSP page compiler * Performance and memory efficiency improvements * Enhanced manager application support for integration with development tools. * Custom Ant tasks to interact with the manager application directly from build.xml scripts. * Many other miscanellous improvements This Release Plan proposes the following schedule: Friday, April 26, 2002 Apache Tomcat 4.1 Beta 1 Friday, May 10, 2002Apache Tomcat 4.1 Beta 2 Friday, May 17, 2002Apache Tomcat 4.1 Release Candidate In order to complete final release, all outstanding Bugzilla bug reports against Tomcat 4.1 above NORMAL severity need to be fixed or deferred for later releases. After the first 4.1 Release Candidate, other RC releases may be made as needed until one is promoted as Final by the Tomcat committers. This Release Plan proposes the following classification of current outstanding bug reports in the bug tracking system, sorted by component and their ID numbers in our bug tracking system at: http://nagoya.apache.org/bugzilla/ Please review the bug reports, and their classification as must have, nice to have, or address later. Lobbying for changes in classification can take place on the TOMCAT-DEV mailing list. In addition, if you have a bug report or enhancement that you wish to have considered prior to final release, please submit a bug report as quickly as possible. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [VOTE] Release Plan for Apache Tomcat 4.1
ballot [X] +1 I approve this plan, and will help Usual rpm packaging, connector stuff for Linux with/without eapi. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
+1 Costin On Wed, 24 Apr 2002, Remy Maucherat wrote: I'd like to call for a vote on the Apache Tomcat 4.1 Release Plan. The vote will run until 04/26, and will be followed, if the Release Plan is accepted, by a vote for the release of Apache Tomcat 4.1 Beta 1. ballot [ ] +1 I approve this plan, and will help [ ] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: /ballot Remy Release Plan for Apache Tomcat 4.1 == Introduction: This document is a release plan for the *final* release of Apache Tomcat 4.1. The goal of the Apache Tomcat 4.1 final release is to provide a stable container that supports 100% of the mandatory requirements of the Servlet 2.3 and JSP 1.2 specifications, as well as to improve and add many useful additional features on top of the existing Apache Tomcat 4.0 releases. Apache Tomcat 4.1 includes the following major new features over Apache Tomcat 4.0: * JMX based administration features * JSP and Struts based administration web application * New Coyote HTTP/1.1 connector * New Coyote JK2 AJP 1.4 connector * Rewritten Jasper JSP page compiler * Performance and memory efficiency improvements * Enhanced manager application support for integration with development tools. * Custom Ant tasks to interact with the manager application directly from build.xml scripts. * Many other miscanellous improvements This Release Plan proposes the following schedule: Friday, April 26, 2002 Apache Tomcat 4.1 Beta 1 Friday, May 10, 2002Apache Tomcat 4.1 Beta 2 Friday, May 17, 2002Apache Tomcat 4.1 Release Candidate In order to complete final release, all outstanding Bugzilla bug reports against Tomcat 4.1 above NORMAL severity need to be fixed or deferred for later releases. After the first 4.1 Release Candidate, other RC releases may be made as needed until one is promoted as Final by the Tomcat committers. This Release Plan proposes the following classification of current outstanding bug reports in the bug tracking system, sorted by component and their ID numbers in our bug tracking system at: http://nagoya.apache.org/bugzilla/ Please review the bug reports, and their classification as must have, nice to have, or address later. Lobbying for changes in classification can take place on the TOMCAT-DEV mailing list. In addition, if you have a bug report or enhancement that you wish to have considered prior to final release, please submit a bug report as quickly as possible. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [VOTE] Release Plan for Apache Tomcat 4.1
ballot [X] +1 I approve this plan, and will help [ ] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: /ballot Larry -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
There are a few additional items I would like to see added. 1. Port my recent mod_jk/apache1.3 new features to mod_jk/Apache2.0 and to jk2 as costin requested. This makes those connectors for use with Apache more consistent. Ok. 2. Resolve a problem Craig mentioned with Context start/stop/reload where not all resources are removed/restarted such as Filters and Listeners. I don't see what you're talking about. If it's the problem with startup/shutdown order, then it has been fixed. 3. Metrics generated that document real performance improvements in Jasper 2 to justify releasing it with Tomcat 4.1. Even if it's not much faster, it is a lot more maintainable and tweakable in the long run. So to test it, we should release it. 4. Implement my recent proposal for jasper 2 so that it recognizes changes to dependent compile time included pages and recompiles the dependent JSP page. This is a frequent problem/question Tomcat users report. Ok. 5. Go through the bug reports and create a FAQ for frequent problems. Include this on the Tomcat site and with the distribution. I have already started work on the framework and some initial FAQ's. Ok. I also think the release schedule is too aggressive. I would like to hold off on a beta 1 until May 10, beta 2 May 24, RC 1 June 3. I'd say I hope it won't be needed, as the HEAD branch has recieved all the bugfixes the main branch had. From the get go, I'd say it should be reasonably stable. So at least to see where we are in terms of stability, I really want to cut a Beta 1 ASAP. If it turns out to be good, then the schedule indicated may be realistic. For example, one of the major new modules (the new HTTP/1.1 connector) has recieved separate testing through Coyote, and has been found to be solid. So I'm optimistic :) I am +1 for doing a release and will help. Thanks :) Remy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
On Wed, 24 Apr 2002, Remy Maucherat wrote: I'd say I hope it won't be needed, as the HEAD branch has recieved all the bugfixes the main branch had. From the get go, I'd say it should be reasonably stable. So at least to see where we are in terms of stability, I really want to cut a Beta 1 ASAP. If it turns out to be good, then the schedule indicated may be realistic. Besides testing done by people who download the nightly builds of Tomcat 4, the HEAD branch code is also the version of Tomcat used in the Java Web Services Developer pack EA1 and EA2 releases, so it has received a very large amount of extra testing both within Sun and from the many people who have downloaded and used the Pack (and that is a sizeable number). Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
- Original Message - From: Remy Maucherat [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 24, 2002 8:44 AM Subject: [VOTE] Release Plan for Apache Tomcat 4.1 I'd like to call for a vote on the Apache Tomcat 4.1 Release Plan. The vote will run until 04/26, and will be followed, if the Release Plan is accepted, by a vote for the release of Apache Tomcat 4.1 Beta 1. [X] +1 I approve this plan, and will help [ ] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
+1 Amy Remy Maucherat wrote: I'd like to call for a vote on the Apache Tomcat 4.1 Release Plan. The vote will run until 04/26, and will be followed, if the Release Plan is accepted, by a vote for the release of Apache Tomcat 4.1 Beta 1. ballot [ ] +1 I approve this plan, and will help [ ] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: /ballot Remy Release Plan for Apache Tomcat 4.1 == Introduction: This document is a release plan for the *final* release of Apache Tomcat 4.1. The goal of the Apache Tomcat 4.1 final release is to provide a stable container that supports 100% of the mandatory requirements of the Servlet 2.3 and JSP 1.2 specifications, as well as to improve and add many useful additional features on top of the existing Apache Tomcat 4.0 releases. Apache Tomcat 4.1 includes the following major new features over Apache Tomcat 4.0: * JMX based administration features * JSP and Struts based administration web application * New Coyote HTTP/1.1 connector * New Coyote JK2 AJP 1.4 connector * Rewritten Jasper JSP page compiler * Performance and memory efficiency improvements * Enhanced manager application support for integration with development tools. * Custom Ant tasks to interact with the manager application directly from build.xml scripts. * Many other miscanellous improvements This Release Plan proposes the following schedule: Friday, April 26, 2002 Apache Tomcat 4.1 Beta 1 Friday, May 10, 2002Apache Tomcat 4.1 Beta 2 Friday, May 17, 2002Apache Tomcat 4.1 Release Candidate In order to complete final release, all outstanding Bugzilla bug reports against Tomcat 4.1 above NORMAL severity need to be fixed or deferred for later releases. After the first 4.1 Release Candidate, other RC releases may be made as needed until one is promoted as Final by the Tomcat committers. This Release Plan proposes the following classification of current outstanding bug reports in the bug tracking system, sorted by component and their ID numbers in our bug tracking system at: http://nagoya.apache.org/bugzilla/ Please review the bug reports, and their classification as must have, nice to have, or address later. Lobbying for changes in classification can take place on the TOMCAT-DEV mailing list. In addition, if you have a bug report or enhancement that you wish to have considered prior to final release, please submit a bug report as quickly as possible. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
On Wed, 24 Apr 2002, Glenn Nielsen wrote: There are a few additional items I would like to see added. 1. Port my recent mod_jk/apache1.3 new features to mod_jk/Apache2.0 and to jk2 as costin requested. This makes those connectors for use with Apache more consistent. mod_jk2 has lower priority - there is no chance it'll be 'release quality' in this time frame. I do hope to have it ready for a beta, but for 4.1 ( and 4.0.x, 3.3.x ) mod_jk1 remains the server connector. coyote-Jk2 is stable as a Ajp13/Socket connector - i.e. all that matter for mod_jk1. The Unix socket and all advanced features of jk2/java will not be 'release quality' either ( but with a bit of luck and some help from Nacho and maybe others we can have them working and beta-level). I also think the release schedule is too aggressive. I would like to hold off on a beta 1 until May 10, beta 2 May 24, RC 1 June 3. We could switch the numbering scheme to follow the 'original' idea - numbered milestones. Like Apache 2 is doing. Instead of beta1, RC1, etc - we'll just use 4.1.0, 4.1.1, etc - with the 'release quality' happening when everyone is happy. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: [VOTE] Release Plan for Apache Tomcat 4.1
+0 Saludos , Ignacio J. Ortega -Mensaje original- De: Remy Maucherat [mailto:[EMAIL PROTECTED]] Enviado el: miércoles 24 de abril de 2002 17:44 Para: [EMAIL PROTECTED] Asunto: [VOTE] Release Plan for Apache Tomcat 4.1 I'd like to call for a vote on the Apache Tomcat 4.1 Release Plan. The vote will run until 04/26, and will be followed, if the Release Plan is accepted, by a vote for the release of Apache Tomcat 4.1 Beta 1. ballot [ ] +1 I approve this plan, and will help [ ] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: /ballot Remy Release Plan for Apache Tomcat 4.1 == Introduction: This document is a release plan for the *final* release of Apache Tomcat 4.1. The goal of the Apache Tomcat 4.1 final release is to provide a stable container that supports 100% of the mandatory requirements of the Servlet 2.3 and JSP 1.2 specifications, as well as to improve and add many useful additional features on top of the existing Apache Tomcat 4.0 releases. Apache Tomcat 4.1 includes the following major new features over Apache Tomcat 4.0: * JMX based administration features * JSP and Struts based administration web application * New Coyote HTTP/1.1 connector * New Coyote JK2 AJP 1.4 connector * Rewritten Jasper JSP page compiler * Performance and memory efficiency improvements * Enhanced manager application support for integration with development tools. * Custom Ant tasks to interact with the manager application directly from build.xml scripts. * Many other miscanellous improvements This Release Plan proposes the following schedule: Friday, April 26, 2002 Apache Tomcat 4.1 Beta 1 Friday, May 10, 2002Apache Tomcat 4.1 Beta 2 Friday, May 17, 2002Apache Tomcat 4.1 Release Candidate In order to complete final release, all outstanding Bugzilla bug reports against Tomcat 4.1 above NORMAL severity need to be fixed or deferred for later releases. After the first 4.1 Release Candidate, other RC releases may be made as needed until one is promoted as Final by the Tomcat committers. This Release Plan proposes the following classification of current outstanding bug reports in the bug tracking system, sorted by component and their ID numbers in our bug tracking system at: http://nagoya.apache.org/bugzilla/ Please review the bug reports, and their classification as must have, nice to have, or address later. Lobbying for changes in classification can take place on the TOMCAT-DEV mailing list. In addition, if you have a bug report or enhancement that you wish to have considered prior to final release, please submit a bug report as quickly as possible. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: [VOTE] Release Plan for Apache Tomcat 4.1
On Thu, 2002-04-25 at 01:44, Remy Maucherat wrote: I'd like to call for a vote on the Apache Tomcat 4.1 Release Plan. The vote will run until 04/26, and will be followed, if the Release Plan is accepted, by a vote for the release of Apache Tomcat 4.1 Beta 1. ballot [ ] +1 I approve this plan, and will help [X] +0 I approve this plan, but can't help [ ] -0 I am not in favor of this plan [ ] -1 I am against this plan, because: /ballot Bojan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
