Great. Sounds like a step in the right direction....
--Olu E.
> -----Original Message-----
> From: James Duncan Davidson [SMTP:[EMAIL PROTECTED]]
> Sent: Sunday, June 13, 1999 2:44 AM
> To: [EMAIL PROTECTED]
> Subject: Re: JSP - beans - configuration quesions
>
> > To make things worse, SUN also did not release adequate documentation to
> > explain the differences
>
> Yes, things are changing. The JSDK is a reference implementation, a
> testbed for new servlet features, and a simple development tool.
>
> The change that involves WEB-INF is leading to a new concept of
> packaging and deployment of web applications that will be present in the
> next version of the specification. Notice the difference between the
> pages served from '/' and '/examples' -- they come from two different
> document roots -- they allow two different areas of a webserver to be
> configured independently of each other -- they allow these hierarchies
> to be moved from one server to another. This will expand in the next
> generation spec to allow an application composed of servlets, html
> pages, jsp, and other things to be deployed at any part of the namespace
> of the server. Furthermore, it is targeted right at ISP use so that end
> users serving pages from ~user directories (or virutal hosted sites) can
> effect servlet mappings, etc.
>
> The default.cfg file is specified now by James Todd in a post. Wan't
> multiple configurations? Use startserver -config myconfig.cfg.
>
> Yes, exploring this territory meant changes in the JSDK. And change is
> sometimes painful. This version of the JSDK was also a total rewrite for
> reasons of modularity (you did check out the source file in /etc that
> allows you to start up a server from any program), use in other Sun
> projects, and a few other things that I can't go into detail yet (go to
> JavaOne to find out). The changes were big. Documentation was light.
>
> To be honest, the target of this release of the JSDK is to make a
> reference implementation servlet engine by which all others can be
> measured in terms of API compliance and to lay the foundation for the
> future. Product level documentation was not possible for this release
> for reasons that I should probably just term "resources" and leave be.
> We are working to fix this for future releases. I will personally make
> sure that the bits and pieces of documentation that have cropped up here
> in the newsgroup make it onto the website somewhere.
>
> .duncan
>
> __________________________________________________________________________
> _
> 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
___________________________________________________________________________
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
