[ANNOUNCEMENT] Tomcat 3.3 Milestone 1

[Larry Isaacs <La...@sas.com>]

The first milestone release of the next version of Tomcat 3.x is available
for download and testing.  As a Tomcat 3.x release, it remains an
implementation of the Servlet 2.2 and JSP 1.1 specifications.

In addition to bug fixes, a large amount of refactoring has gone into
Tomcat 3.3m1 since Tomcat 3.2. Much of the code is still there, but cleaned
up and likely in a new location. It is hoped with the changes that have
occurred, you will find Tomcat 3.3 more flexible and easier to configure.
You should also find improved performance over Tomcat 3.2.

In this milestone release, documentation hasn't caught up with some of the more
recent changes to Tomcat 3.3m1.  For this reason, be sure to read the "README"
file found in Tomcat's "doc" directory.  It contains documentation that covers
some of the more important of these recent changes to Tomcat 3.3.

In addition to the "README" file, the following notes provide some additional
information you will need to make full use of this release:

1) The binary distribution has source for the connectors, but not for the
   Tomcat container.  The source for the full jakarta-tomcat CVS tree is
   available separately in the "v3.3-m1/src" directory.

2) The internal directory structure contained in the binary and source archives
   differs from Tomcat 3.2.  The binary expands to a directory called "tomcat"
   and the source expands to "jakarta-tomcat".  This matches what you would get
   if you checked out CVS source and built Tomcat from that source.

3) The new class loader scheme in this release ignores your CLASSPATH setting.
   Instead, you are expected to add needed jars to Tomcat's "lib", "lib/common",
   and "lib/shared" directories. See the "README" file in Tomcat's "doc"
   directory for details.

4) The "sanity-test" is not part of the binary distribution like it was with
   Tomcat 3.2.  However, it is available in "War" form, along with the
   Watchdog JSP and servlet tests.  These are found in the "v3.3-m1/apps"
   directory.  Place these War files in Tomcat's "webapps" directory before
   starting Tomcat. To simplify testing, these tests can be run from the Admin
   web application. See the "README" file in Tomcat's "doc" directory for details.

5) On Windows 9x, there have been instances where the watchdog-jsp.jsp test
   failed to run when the jsp was first compiled.  If this happens, try
   refreshing the page to get the test to run.  Note: There is one expected
   failure, "positiveScriptlet.jsp", when the watchdog-jsp.jsp test is run again
   without restarting Tomcat 3.3.

6) For the watchdog-servlet.jsp test file to run, you must copy
   jakarta-tools' "moo.jar" and jakarta-watchdog's "client.jar" to Tomcat's
   "webapps/admin/WEB-INF/lib" directory before starting Tomcat.  Both of these
   jars are found in the "v3.3-m1/bin" directory.  These will be included in
   the admin.war in the next release.

7) The Admin web application's index.html file has an error in the commands
   it displays to set it to "trusted".  "run" should appear before "-enableAdmin"
   when using the ".sh" and ".bat" files.  This is documented correctly in
   the "README" in the "doc" directory.

Please download this release and give it a try in your environment.  The source,
rpms, and binaries may be found at:

    http://jakarta.apache.org/builds/tomcat/release/v3.3-m1

To log problems or bugs, as well as submit patches, please refer to:

    http://jakarta.apache.org/site/bugs.html

When logging bugs to Bugzilla, please specify the Program as "Tomcat 3"  and
the Version as "Nightly Build".

I would like to thank all those who have volunteered their time and efforts to
bring Tomcat 3.3m1 to this point. I look forward to continuing the effort to
bring Tomcat 3.3 to a final release.

Thanks,
Larry Isaacs

Re: [ANNOUNCEMENT] Tomcat 3.3 Milestone 1

[Alex Fernández <af...@tid.es>]

Sorry, this was meant to be sent to Larry alone.

Alex.

Re: [ANNOUNCEMENT] Tomcat 3.3 Milestone 1

[Alex Fernández <af...@tid.es>]

Hi Larry!

I have tested part of our application with Tomcat 3.3, and it works like a charm.
Everything works all right, though it's only the administration servlets. I'll be
testing the load-test part in short.

The testing has been done on Windows 2000 with Sun's JDK 1.2.2. Later I'll try it on
Solaris with Sun's JDK 1.3. If you would like different JDK's tested, just say it.

Thanks for your work, it's really impressive. I had never seen a milestone release
that installed and worked so smoothly.

Un saludo,

Alex.

Larry Isaacs wrote:

> The first milestone release of the next version of Tomcat 3.x is available
> for download and testing.  As a Tomcat 3.x release, it remains an
> implementation of the Servlet 2.2 and JSP 1.1 specifications.
>
> In addition to bug fixes, a large amount of refactoring has gone into
> Tomcat 3.3m1 since Tomcat 3.2. Much of the code is still there, but cleaned
> up and likely in a new location. It is hoped with the changes that have
> occurred, you will find Tomcat 3.3 more flexible and easier to configure.
> You should also find improved performance over Tomcat 3.2.
>
> In this milestone release, documentation hasn't caught up with some of the more
> recent changes to Tomcat 3.3m1.  For this reason, be sure to read the "README"
> file found in Tomcat's "doc" directory.  It contains documentation that covers
> some of the more important of these recent changes to Tomcat 3.3.
>
> In addition to the "README" file, the following notes provide some additional
> information you will need to make full use of this release:
>
> 1) The binary distribution has source for the connectors, but not for the
>    Tomcat container.  The source for the full jakarta-tomcat CVS tree is
>    available separately in the "v3.3-m1/src" directory.
>
> 2) The internal directory structure contained in the binary and source archives
>    differs from Tomcat 3.2.  The binary expands to a directory called "tomcat"
>    and the source expands to "jakarta-tomcat".  This matches what you would get
>    if you checked out CVS source and built Tomcat from that source.
>
> 3) The new class loader scheme in this release ignores your CLASSPATH setting.
>    Instead, you are expected to add needed jars to Tomcat's "lib", "lib/common",
>    and "lib/shared" directories. See the "README" file in Tomcat's "doc"
>    directory for details.
>
> 4) The "sanity-test" is not part of the binary distribution like it was with
>    Tomcat 3.2.  However, it is available in "War" form, along with the
>    Watchdog JSP and servlet tests.  These are found in the "v3.3-m1/apps"
>    directory.  Place these War files in Tomcat's "webapps" directory before
>    starting Tomcat. To simplify testing, these tests can be run from the Admin
>    web application. See the "README" file in Tomcat's "doc" directory for details.
>
> 5) On Windows 9x, there have been instances where the watchdog-jsp.jsp test
>    failed to run when the jsp was first compiled.  If this happens, try
>    refreshing the page to get the test to run.  Note: There is one expected
>    failure, "positiveScriptlet.jsp", when the watchdog-jsp.jsp test is run again
>    without restarting Tomcat 3.3.
>
> 6) For the watchdog-servlet.jsp test file to run, you must copy
>    jakarta-tools' "moo.jar" and jakarta-watchdog's "client.jar" to Tomcat's
>    "webapps/admin/WEB-INF/lib" directory before starting Tomcat.  Both of these
>    jars are found in the "v3.3-m1/bin" directory.  These will be included in
>    the admin.war in the next release.
>
> 7) The Admin web application's index.html file has an error in the commands
>    it displays to set it to "trusted".  "run" should appear before "-enableAdmin"
>    when using the ".sh" and ".bat" files.  This is documented correctly in
>    the "README" in the "doc" directory.
>
> Please download this release and give it a try in your environment.  The source,
> rpms, and binaries may be found at:
>
>     http://jakarta.apache.org/builds/tomcat/release/v3.3-m1
>
> To log problems or bugs, as well as submit patches, please refer to:
>
>     http://jakarta.apache.org/site/bugs.html
>
> When logging bugs to Bugzilla, please specify the Program as "Tomcat 3"  and
> the Version as "Nightly Build".
>
> I would like to thank all those who have volunteered their time and efforts to
> bring Tomcat 3.3m1 to this point. I look forward to continuing the effort to
> bring Tomcat 3.3 to a final release.
>
> Thanks,
> Larry Isaacs
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, email: tomcat-dev-help@jakarta.apache.org

Re: [ANNOUNCEMENT] Tomcat 3.3 Milestone 1

["Craig R. McClanahan" <Cr...@eng.sun.com>]

Stuart Thomson wrote:

> > 3) The new class loader scheme in this release ignores your CLASSPATH setting.
> >    Instead, you are expected to add needed jars to Tomcat's "lib", "lib/common",
> >    and "lib/shared" directories. See the "README" file in Tomcat's "doc"
> >    directory for details.
>
> This will probably stop me from ever going to Tomcat 3.3. Finding
> classes on the classpath is very convenient at development time.
>

You will find that Tomcat 4.0 has a similar restriction -- the CLASSPATH environment
variable passed in to tomcat.bat or tomcat.sh is totally ignored, and any user JARs in
the "lib" directory are automatically made available to all web applications.

Experience has shown that CLASSPATH problems account for nearly all newbie problems
other than the ones related to mod_jk or mod_jserv (that means well over half the
problem reports are related to this).  Having a clear policy on what is included makes
life much simpler for newcomers (who don't always understand what a CLASSPATH really
does) to get set up.

People who know they want to include other things are also free to modify the standard
startup scripts -- but they are also expected to know enough to keep themselves out of
trouble.

Craig McClanahan

Re: [ANNOUNCEMENT] Tomcat 3.3 Milestone 1

[Stuart Thomson <st...@swtsoft.demon.co.uk>]

> 3) The new class loader scheme in this release ignores your CLASSPATH setting.
>    Instead, you are expected to add needed jars to Tomcat's "lib", "lib/common",
>    and "lib/shared" directories. See the "README" file in Tomcat's "doc"
>    directory for details.

This will probably stop me from ever going to Tomcat 3.3. Finding
classes on the classpath is very convenient at development time.

Re: [ANNOUNCEMENT] Tomcat 3.3 Milestone 1

[Jon Stevens <jo...@latchkey.com>]

on 2/15/01 9:57 AM, "Larry Isaacs" <La...@sas.com> wrote:

> I would like to thank all those who have volunteered their time and efforts to
> bring Tomcat 3.3m1 to this point. I look forward to continuing the effort to
> bring Tomcat 3.3 to a final release.
> 
> Thanks,
> Larry Isaacs

Wow, that was a headache of a process to go through <smile>, but I just want
to say: 

Congrats.

I think that this project is MUCH more on track these days than it was
previously. :-)

-jon

-- 
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/> && <http://java.apache.org/turbine/>

AW: [ANNOUNCEMENT] Tomcat 3.3 Milestone 1

[Juergen Fey <jf...@xerpent.com>]

> 3) The new class loader scheme in this release ignores your 
> CLASSPATH setting.
>    Instead, you are expected to add needed jars to Tomcat's 
> "lib", "lib/common",
>    and "lib/shared" directories. See the "README" file in Tomcat's "doc"
>    directory for details.
> 

It took a while to arrange JARs in the classpath in the right order 
since i am using Xerces, JAPX and JDOM in my app. 
How would i arrange these in the directories?

Juergen