[ANNOUNCE] Nightly Builds of Tomcat 4.0-dev (pre-alpha)

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

Effective immediately, adventerous souls can download a nightly build of
the Tomcat 4.0-dev development tree (which is being updated to support
the new Servlet 2.3 and JSP 1.2 draft specifications).  The binary
distributions are available from:

    http://jakarta.apache.org/builds/jakarta-tomcat-4.0/nightly

and the source code distributions are at:

    http://jakarta.apache.org/builds/jakarta-tomcat-4.0/nightly/src

These builds correspond to the source code that is in the
"jakarta-tomcat-4.0" module in CVS.  They also include the most recent
versions of the servlet 2.3 and JSP 1.2 API classes (servlet.jar).  Any
web application that is compliant with servlet 2.2 and JSP 1.1 should
run fine under these builds (failure to do so is a bug in Tomcat 4.0
that should be reported), or you can start experimenting with the new
features like as application events and filters.

To keep track of what new features have been implemented so far, check
out the file "NEW_SPECS.txt" in the top level directory.

NOTE:  You should use this code to help us debug Tomcat 4.0, and/or
to start learning about the new servlet 2.3 and JSP 1.2 spec features
that are being added.  It is not yet appropriate to use this code
for production purposes.  The goal is to have a beta-quality version
of this code (with complete support for all the 2.3/1.2 features, as
of the current drafts of the spec at that time) by ApacheCon London,
October 23-25, 2000.

Craig McClanahan

====================
See you at ApacheCon Europe <http://www.apachecon.com>!
Session VS01 (23-Oct 13h00-17h00):  Sun Technical Briefing
Session T06  (24-Oct 14h00-15h00):  Migrating Apache JServ
                                    Applications to Tomcat

Re: [ANNOUNCE] Nightly Builds of Tomcat 4.0-dev (pre-alpha)

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

Johan Peeters wrote:

> "Craig R. McClanahan" wrote:
>
> ...
>
> > finalized.  However, Tomcat 4.0 recognizes the following DOCTYPE
> > declaration and uses its internal draft version of the new DTD:
> >
> >     <!DOCTYPE web-app
> >         PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
> >         "http://java.sun.com/j2ee/dtds/web-app_2_3.dtd">
> >
> > because it matches on the public identifier.  To avoid cut-and-paste
> > problems, you can copy this from one of the example web applications.
> >
>
> I found myself modifying the above lines in the webdav app's deployment
> descriptor in the distribution to
>     <!DOCTYPE web-app
>         PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
>         "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
>
> to get webdav to load.
>

I can run "http://localhost:8080/webdav" just fine on RH 6.2, JDK 1.2.2,
Tomcat 4.0 -- see more below.

>
> >
> > >    * tomcat seems to be listening to port 0, rather than 8080, in
> > >      spite of the standard
> > >        <Connector
> > >      className="org.apache.catalina.connector.http.HttpConnector"
> > >                   port="8080" minProcessors="5" maxProcessors="75"
> > >                   acceptCount="10" debug="2"/>
> > >      in server.xml.
> > >
> >
> > How are you making that determination?  Does it not respond to 8080 for
> > you?  What platform/OS/JDK?
> >
>
> It does not respond to 8080. Tomcat writes
>
> PoolTcpConnector: Starting HttpConnectionHandler on 0
>
> to stdout when starting. Interestingly, netstat does not show anyone
> listening on port 0 :-).
> OS=NT, JDK=1.2.2
>

Well, that's really interesting.  Especially, considering the fact that Tomcat
4.0 doesn't use PoolTcpConnector, doesn't have a class named
HttpConnectionHandler in it, and only writes a version identifier (Apache
Tomcat 4.0-dev) to standard output when it starts up).  Those classes are both
used in Tomcat 3.x, however.  Are you sure you are using the
"jakarta-tomcat-4.0" module, and have nothing related to Tomcat 3.x in your
classpath?  And starting it with "%CATALINA_HOME%\bin\catalina start"?

Craig

====================
See you at ApacheCon Europe <http://www.apachecon.com>!
Session VS01 (23-Oct 13h00-17h00):  Sun Technical Briefing
Session T06  (24-Oct 14h00-15h00):  Migrating Apache JServ
                                    Applications to Tomcat

Re: [ANNOUNCE] Nightly Builds of Tomcat 4.0-dev (pre-alpha)

[Johan Peeters <jo...@alcatel.be>]

"Craig R. McClanahan" wrote:

...

> finalized.  However, Tomcat 4.0 recognizes the following DOCTYPE
> declaration and uses its internal draft version of the new DTD:
>
>     <!DOCTYPE web-app
>         PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
>         "http://java.sun.com/j2ee/dtds/web-app_2_3.dtd">
>
> because it matches on the public identifier.  To avoid cut-and-paste
> problems, you can copy this from one of the example web applications.
>

I found myself modifying the above lines in the webdav app's deployment
descriptor in the distribution to
    <!DOCTYPE web-app
        PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
        "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">

to get webdav to load.

>
> >    * tomcat seems to be listening to port 0, rather than 8080, in
> >      spite of the standard
> >        <Connector
> >      className="org.apache.catalina.connector.http.HttpConnector"
> >                   port="8080" minProcessors="5" maxProcessors="75"
> >                   acceptCount="10" debug="2"/>
> >      in server.xml.
> >
>
> How are you making that determination?  Does it not respond to 8080 for
> you?  What platform/OS/JDK?
>

It does not respond to 8080. Tomcat writes

PoolTcpConnector: Starting HttpConnectionHandler on 0

to stdout when starting. Interestingly, netstat does not show anyone
listening on port 0 :-).
OS=NT, JDK=1.2.2

>
> >
> >
> > I still do not quite understand the relationship between tomcat and
> > catalina. I notice that in the package structure 'tomcat' has been
> > replaced with 'catalina' everywhere. Will the name catalina persist or
> > will this be replaced by tomcat by the time that 4.0 is goes to
> > beta/is released? Will the future product be known as Tomcat or
> > Catalina?
> >
>
> Catalina is the servlet container piece of Tomcat 4.0, analogous to
> Jasper which is the JSP piece.
>
> Tomcat = Servlet + JSP, so Tomcat = Catalina + Jasper.
>
> >
> > Many Thanks,
> >
> > Yo
> >
>
> Craig McClanahan
>
> ====================
> See you at ApacheCon Europe <http://www.apachecon.com>!
> Session VS01 (23-Oct 13h00-17h00):  Sun Technical Briefing
> Session T06  (24-Oct 14h00-15h00):  Migrating Apache JServ
>                                     Applications to Tomcat

--
Johan Peeters mailto:johan.peeters@alcatel.be
Software Architect - Net Commerce
Alcatel - Gen. De Wittelaan 11 A bus 1 - 2800 Mechelen - Belgium
Phone: +32 15 29 3427 Fax: +32 3 240 4800

Re: [ANNOUNCE] Nightly Builds of Tomcat 4.0-dev (pre-alpha)

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

Johan Peeters wrote:

> I downloaded and tried to run the latest nightly build. I encountered
> following problems:
>
>    * when loading the webdav app, there is a problem with the
>      web-app_2_3.dtd - it seems not to be available yet on
>      java.sun.com. A workaround is to roll back to the 2_2 dtd. I was
>      surprised to find that the DTD is actually needed. Presumably
>      some xml parsing is done in validating mode?
>

The "official" DTD will not get published until the 2.3 spec is
finalized.  However, Tomcat 4.0 recognizes the following DOCTYPE
declaration and uses its internal draft version of the new DTD:

    <!DOCTYPE web-app
        PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
        "http://java.sun.com/j2ee/dtds/web-app_2_3.dtd">

because it matches on the public identifier.  To avoid cut-and-paste
problems, you can copy this from one of the example web applications.

NOTE:  Any servlet 2.2/JSP 1.1 application should continue to work under
Tomcat 4.0 -- failure to do this is a bug that should be reported.

>    *
>    * tomcat seems to be listening to port 0, rather than 8080, in
>      spite of the standard
>        <Connector
>      className="org.apache.catalina.connector.http.HttpConnector"
>                   port="8080" minProcessors="5" maxProcessors="75"
>                   acceptCount="10" debug="2"/>
>      in server.xml.
>

How are you making that determination?  Does it not respond to 8080 for
you?  What platform/OS/JDK?

>
>
> I still do not quite understand the relationship between tomcat and
> catalina. I notice that in the package structure 'tomcat' has been
> replaced with 'catalina' everywhere. Will the name catalina persist or
> will this be replaced by tomcat by the time that 4.0 is goes to
> beta/is released? Will the future product be known as Tomcat or
> Catalina?
>

Catalina is the servlet container piece of Tomcat 4.0, analogous to
Jasper which is the JSP piece.

Tomcat = Servlet + JSP, so Tomcat = Catalina + Jasper.

>
> Many Thanks,
>
> Yo
>

Craig McClanahan

====================
See you at ApacheCon Europe <http://www.apachecon.com>!
Session VS01 (23-Oct 13h00-17h00):  Sun Technical Briefing
Session T06  (24-Oct 14h00-15h00):  Migrating Apache JServ
                                    Applications to Tomcat

Re: [ANNOUNCE] Nightly Builds of Tomcat 4.0-dev (pre-alpha)

[Johan Peeters <jo...@alcatel.be>]

I downloaded and tried to run the latest nightly build. I encountered
following problems:

   * when loading the webdav app, there is a problem with the
     web-app_2_3.dtd - it seems not to be available yet on java.sun.com.
     A workaround is to roll back to the 2_2 dtd. I was surprised to
     find that the DTD is actually needed. Presumably some xml parsing
     is done in validating mode?
   * tomcat seems to be listening to port 0, rather than 8080, in spite
     of the standard
       <Connector
     className="org.apache.catalina.connector.http.HttpConnector"
                  port="8080" minProcessors="5" maxProcessors="75"
                  acceptCount="10" debug="2"/>
     in server.xml.

I still do not quite understand the relationship between tomcat and
catalina. I notice that in the package structure 'tomcat' has been
replaced with 'catalina' everywhere. Will the name catalina persist or
will this be replaced by tomcat by the time that 4.0 is goes to beta/is
released? Will the future product be known as Tomcat or Catalina?

Many Thanks,

Yo

--
Johan Peeters mailto:johan.peeters@alcatel.be
Software Architect - Net Commerce
Alcatel - Gen. De Wittelaan 11 A bus 1 - 2800 Mechelen - Belgium
Phone: +32 15 29 3427 Fax: +32 3 240 4800

Re: [ANNOUNCE] Nightly Builds of Tomcat 4.0-dev (pre-alpha)

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

David Geary wrote:

> I downloaded the binary distribution of Tomcat 4.0, but when I try to run
> the MS-DOS startup file in the bin directory, I get an MS-DOS window that
> appears for a split second and then disappears.

This usually means that your DOS windows are not configured with enough
room
for environment variables.  You can modify this by creating a config.sys
file
in c:\ with the following contents, and rebooting:

    shell=c:\command.com c:\ e:/4096 /p

You can also type this command:

    %CATALINA_HOME%\bin\catalina run

to run in the same DOS window instead of a new one.  You should then be
able to
see any error message that is produced.

NOTE 1:  The DOS command lines for starting Tomcat 3.2 and 4.0 have been
undergoing some churn lately, as we try to deal with the differences
between
Win98, WinNT, and W2K -- each platform exhibits different quirks; so
much for
"compatibility" :-).  Which particular platform are you trying to run
on?
(Follow-ups to this should be sent to TOMCAT-USER only).

NOTE 2:  When released, Tomcat 4.0 will include much nicer support for
running
under WIndows, including a toolbar icon for starting, stopping, and
restarting
it.  Until this package is finished, we're still stuck with command line
issues.

>
> I'm not sure what "catalina" is (the code name for Tomcat 4.0?), but when I
> try to run the catalina MS-DOS file in the bin directory, I get the same
> result as with the startup file.

Catalina is the servlet container portion of Tomcat 4.0, to go along
with
Jasper (the JSP engine portion).

Tomcat = Servlets + JSP

>
> I have no difficulty using Tomcat 3.1 and a handful of other Web servers
> such as Resin. Can anyone shed some light on this problem?
>
> david
>

Craig

====================
See you at ApacheCon Europe <http://www.apachecon.com>!
Session VS01 (23-Oct 13h00-17h00):  Sun Technical Briefing
Session T06  (24-Oct 14h00-15h00):  Migrating Apache JServ
                                    Applications to Tomcat

Re: [ANNOUNCE] Nightly Builds of Tomcat 4.0-dev (pre-alpha)

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

David Geary wrote:

> I downloaded the binary distribution of Tomcat 4.0, but when I try to run
> the MS-DOS startup file in the bin directory, I get an MS-DOS window that
> appears for a split second and then disappears.

This usually means that your DOS windows are not configured with enough
room
for environment variables.  You can modify this by creating a config.sys
file
in c:\ with the following contents, and rebooting:

    shell=c:\command.com c:\ e:/4096 /p

You can also type this command:

    %CATALINA_HOME%\bin\catalina run

to run in the same DOS window instead of a new one.  You should then be
able to
see any error message that is produced.

NOTE 1:  The DOS command lines for starting Tomcat 3.2 and 4.0 have been
undergoing some churn lately, as we try to deal with the differences
between
Win98, WinNT, and W2K -- each platform exhibits different quirks; so
much for
"compatibility" :-).  Which particular platform are you trying to run
on?
(Follow-ups to this should be sent to TOMCAT-USER only).

NOTE 2:  When released, Tomcat 4.0 will include much nicer support for
running
under WIndows, including a toolbar icon for starting, stopping, and
restarting
it.  Until this package is finished, we're still stuck with command line
issues.

>
> I'm not sure what "catalina" is (the code name for Tomcat 4.0?), but when I
> try to run the catalina MS-DOS file in the bin directory, I get the same
> result as with the startup file.

Catalina is the servlet container portion of Tomcat 4.0, to go along
with
Jasper (the JSP engine portion).

Tomcat = Servlets + JSP

>
> I have no difficulty using Tomcat 3.1 and a handful of other Web servers
> such as Resin. Can anyone shed some light on this problem?
>
> david
>

Craig

====================
See you at ApacheCon Europe <http://www.apachecon.com>!
Session VS01 (23-Oct 13h00-17h00):  Sun Technical Briefing
Session T06  (24-Oct 14h00-15h00):  Migrating Apache JServ
                                    Applications to Tomcat

Re: [ANNOUNCE] Nightly Builds of Tomcat 4.0-dev (pre-alpha)

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

David Geary wrote:

> I downloaded the binary distribution of Tomcat 4.0, but when I try to run
> the MS-DOS startup file in the bin directory, I get an MS-DOS window that
> appears for a split second and then disappears.

This usually means that your DOS windows are not configured with enough
room
for environment variables.  You can modify this by creating a config.sys
file
in c:\ with the following contents, and rebooting:

    shell=c:\command.com c:\ e:/4096 /p

You can also type this command:

    %CATALINA_HOME%\bin\catalina run

to run in the same DOS window instead of a new one.  You should then be
able to
see any error message that is produced.

NOTE 1:  The DOS command lines for starting Tomcat 3.2 and 4.0 have been
undergoing some churn lately, as we try to deal with the differences
between
Win98, WinNT, and W2K -- each platform exhibits different quirks; so
much for
"compatibility" :-).  Which particular platform are you trying to run
on?
(Follow-ups to this should be sent to TOMCAT-USER only).

NOTE 2:  When released, Tomcat 4.0 will include much nicer support for
running
under WIndows, including a toolbar icon for starting, stopping, and
restarting
it.  Until this package is finished, we're still stuck with command line
issues.

>
> I'm not sure what "catalina" is (the code name for Tomcat 4.0?), but when I
> try to run the catalina MS-DOS file in the bin directory, I get the same
> result as with the startup file.

Catalina is the servlet container portion of Tomcat 4.0, to go along
with
Jasper (the JSP engine portion).

Tomcat = Servlets + JSP

>
> I have no difficulty using Tomcat 3.1 and a handful of other Web servers
> such as Resin. Can anyone shed some light on this problem?
>
> david
>

Craig

====================
See you at ApacheCon Europe <http://www.apachecon.com>!
Session VS01 (23-Oct 13h00-17h00):  Sun Technical Briefing
Session T06  (24-Oct 14h00-15h00):  Migrating Apache JServ
                                    Applications to Tomcat

Re: [ANNOUNCE] Nightly Builds of Tomcat 4.0-dev (pre-alpha)

[David Geary <sa...@tri-lakesonline.net>]

I downloaded the binary distribution of Tomcat 4.0, but when I try to run
the MS-DOS startup file in the bin directory, I get an MS-DOS window that
appears for a split second and then disappears.

I'm not sure what "catalina" is (the code name for Tomcat 4.0?), but when I
try to run the catalina MS-DOS file in the bin directory, I get the same
result as with the startup file.

I have no difficulty using Tomcat 3.1 and a handful of other Web servers
such as Resin. Can anyone shed some light on this problem?


david

"Craig R. McClanahan" wrote:

> Effective immediately, adventerous souls can download a nightly build of
> the Tomcat 4.0-dev development tree (which is being updated to support
> the new Servlet 2.3 and JSP 1.2 draft specifications).  The binary
> distributions are available from:
>
>     http://jakarta.apache.org/builds/jakarta-tomcat-4.0/nightly
>
> and the source code distributions are at:
>
>     http://jakarta.apache.org/builds/jakarta-tomcat-4.0/nightly/src
>
> These builds correspond to the source code that is in the
> "jakarta-tomcat-4.0" module in CVS.  They also include the most recent
> versions of the servlet 2.3 and JSP 1.2 API classes (servlet.jar).  Any
> web application that is compliant with servlet 2.2 and JSP 1.1 should
> run fine under these builds (failure to do so is a bug in Tomcat 4.0
> that should be reported), or you can start experimenting with the new
> features like as application events and filters.
>
> To keep track of what new features have been implemented so far, check
> out the file "NEW_SPECS.txt" in the top level directory.
>
> NOTE:  You should use this code to help us debug Tomcat 4.0, and/or
> to start learning about the new servlet 2.3 and JSP 1.2 spec features
> that are being added.  It is not yet appropriate to use this code
> for production purposes.  The goal is to have a beta-quality version
> of this code (with complete support for all the 2.3/1.2 features, as
> of the current drafts of the spec at that time) by ApacheCon London,
> October 23-25, 2000.
>
> Craig McClanahan
>
> ====================
> See you at ApacheCon Europe <http://www.apachecon.com>!
> Session VS01 (23-Oct 13h00-17h00):  Sun Technical Briefing
> Session T06  (24-Oct 14h00-15h00):  Migrating Apache JServ
>                                     Applications to Tomcat

Re: [ANNOUNCE] Nightly Builds of Tomcat 4.0-dev (pre-alpha)

[Johan Peeters <jo...@alcatel.be>]

Craig,

That certainly would help to introduce the new releases seamlessly in our
development environment.
What about the tag library problem that Yun reported and I also encountered? Is it
a bug? Any fixes in the near future?

Thanks,

Yo

"Craig R. McClanahan" wrote:

> Johan Peeters wrote:
>
> > Taking full credit for my own stupidity, I am not sure of the wisdom of
> > superceeding tomcat.bat with catalina.bat.
> >
>
> That's a good point.
>
> The reasoning went like this -- some people wanted to package the servlet
> container part of Tomcat with template technologies other than JSP.  In order
> to do this, we have separated the major pieces (servlet container, JSP engine,
> and web applications) in the source code directories -- which required that we
> give the pieces names (Catalina for the servlet container, since that was the
> name of the proposal that originated this source code, and Jasper for the JSP
> engine, because it was the historical name used before the code was contributed
> to Apache).  But, if you were running separately, you needed a startup script
> that started the component you were actually talking about  -- Catalina.
>
> Tomcat was, is, and will be *both* servlet container and JSP (i.e. both
> Catalina and Jasper will be included on the inside).
>
> I'm going to add "tomcat.sh" and "tomcat.bat" scripts that can be used for
> startups, so that others won't stumble across this confusion the same way that
> Johann did.  However, so that you can have both Tomcat 3.2 and Tomcat 4.0
> installed on the same system, I suggest we maintain the CATALINA_HOME
> environment variable name for the Tomcat 4.0 startup scripts.
>
> >
> > Best Wishes,
> >
> > Yo
> >
>
> Craig McClanahan
>
> ====================
> See you at ApacheCon Europe <http://www.apachecon.com>!
> Session VS01 (23-Oct 13h00-17h00):  Sun Technical Briefing
> Session T06  (24-Oct 14h00-15h00):  Migrating Apache JServ
>                                     Applications to Tomcat

--
Johan Peeters Software Architect
moving soon - to stay in touch
mailto:johan.peeters@technologist.com

Re: [ANNOUNCE] Nightly Builds of Tomcat 4.0-dev (pre-alpha)

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

Johan Peeters wrote:

> Taking full credit for my own stupidity, I am not sure of the wisdom of
> superceeding tomcat.bat with catalina.bat.
>

That's a good point.

The reasoning went like this -- some people wanted to package the servlet
container part of Tomcat with template technologies other than JSP.  In order
to do this, we have separated the major pieces (servlet container, JSP engine,
and web applications) in the source code directories -- which required that we
give the pieces names (Catalina for the servlet container, since that was the
name of the proposal that originated this source code, and Jasper for the JSP
engine, because it was the historical name used before the code was contributed
to Apache).  But, if you were running separately, you needed a startup script
that started the component you were actually talking about  -- Catalina.

Tomcat was, is, and will be *both* servlet container and JSP (i.e. both
Catalina and Jasper will be included on the inside).

I'm going to add "tomcat.sh" and "tomcat.bat" scripts that can be used for
startups, so that others won't stumble across this confusion the same way that
Johann did.  However, so that you can have both Tomcat 3.2 and Tomcat 4.0
installed on the same system, I suggest we maintain the CATALINA_HOME
environment variable name for the Tomcat 4.0 startup scripts.

>
> Best Wishes,
>
> Yo
>

Craig McClanahan

====================
See you at ApacheCon Europe <http://www.apachecon.com>!
Session VS01 (23-Oct 13h00-17h00):  Sun Technical Briefing
Session T06  (24-Oct 14h00-15h00):  Migrating Apache JServ
                                    Applications to Tomcat

Re: [ANNOUNCE] Nightly Builds of Tomcat 4.0-dev (pre-alpha)

[Johan Peeters <jo...@alcatel.be>]

Yun Sang Jung wrote:

> ...
> [Problem3]
> When I run jsp simple custom tag example
> ->
> A Servlet Exception Has Occurred
> org.apache.jasper.compiler.CompileException:
> c:\navidad\jakarta-tomcat-4.0\webapps\examples\jsp\simpletag\foo.jsp(6,0)
> Unable to open taglibrary
> http://java.apache.org/tomcat/examples-taglib : Parse Error in the tag
> library descriptor: External entity not found:
> "http://java.sun.com/j2ee/dtds/web-app_2_3.dtd".
>
> I think it is a same problem which is pointed by Johan Peeters.

I did indeed have an issue early on with the 2.3 DTD, but as Craig
pointed out, I screwed up running a version which had some 3.x
components. More particularly, I started tomcat by using the 3.2
tomcat.bat script instead of catalina.bat, so I am not sure what the
problems concerning webdav were related to. However, running a 'pure'
4.0 version, I have the same problems as Yun with custom tags.

Taking full credit for my own stupidity, I am not sure of the wisdom of
superceeding tomcat.bat with catalina.bat.

Best Wishes,

Yo

--
Johan Peeters mailto:johan.peeters@alcatel.be
Software Architect - Net Commerce
Alcatel - Gen. De Wittelaan 11 A bus 1 - 2800 Mechelen - Belgium
Phone: +32 15 29 3427 Fax: +32 3 240 4800

Questions On How To Handle Image