On Sun, 1 Apr 2001, Mark Galbreath wrote:
> Thanks for the clarification! I actually knew this already, but
> missed the JSWDK part. I tried to get JRun 3.0 merged with IIS 5.0
> but after 2 days of configuration hassles gave up and went back to
> Tomcat 3.2.1. And it's a big hassle as well. I like the idea of
> web applications, and I guess it just takes some getting used to
> having a hierarchical directory structure and deployment mechanism
> like Ant + half-a dozen XML config files to maintain. While granted
> JSDK was never intended to be a production reference, having the
> servlet container bundled with the classes and API sure was
> convenient. But then, now there's J2SDKEE 1.3.....
I recently switched over to using Tomcat (I was using ServletExec
previously), and I've found the tomcat-user mailing list quite helpful
in getting some things figured out. There's a page off
jakarta.apache.org that has info about the mailing lists (inlcuding
archives -- although try the "Mailing List Archives" link instead of
the "Tomcat-User Archive" one, it has a better interface). Plus there
is some decent documentation on that site as well (although it may
take a little poking around as well). And some people on that mailing
list have set up their own documentation web pages.
> ----- Original Message -----
> From: "Milt Epstein" <[EMAIL PROTECTED]>
> Sent: Sunday, April 01, 2001 11:06 AM
>
>
> > On Sat, 31 Mar 2001, Mark Galbreath wrote:
> >
> > > Doh! How did this slip by me??? I've seen nothing about this on
> > > Sun's site.
> >
> > Don't get too excited by this -- I believe it is something that
> > existed for only a short while, and is no longer actively supported
> > (which probably explains why a lot of people aren't so aware of it).
> > IIRC, originally, there was just the JSDK (through JSDK 2.1). It
> > included the "servletrunner" facility to run servlets, but that wasn't
> > really a web server or something that was intended for a production
> > environment. Separately, there was the JWS (Java Web Server), which
> > implemented/supported the JSDK. Then they rolled that all into one
> > (and JSP was included at some point), and that's what the JSWDK
> > is/was. But shortly after that, Jakarta came along, and now Tomcat is
> > the official reference implementation of the JSDK/JSP spec (for spec
> > versions 2.2 and beyond). And JWS is no longer actively supported.
> >
> > Anyway, I think for anyone getting into servlets at this point, Tomcat
> > (or some third party serlvet container that implements at least the
> > 2.2 spec) is the way to go. Separate JSDK's and/or JSWDK's are to be
> > avoided -- they're not current, and they're not actively supported.
> > Plus there were some relatively significant changes from the 2.1 to
> > 2.2 specs (e.g. the whole idea of "web applications").
> >
> > I'm sure I'll be corrected if I have any of this wrong :-).
[ ... ]
Milt Epstein
Research Programmer
Software/Systems Development Group
Computing and Communications Services Office (CCSO)
University of Illinois at Urbana-Champaign (UIUC)
[EMAIL PROTECTED]
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
