JSP Add-On Module 1.1.2 for LiteWebServer (LWS) 3.0 Release Notes
=================================================================

* The o.a.c.u.ResourceSet class has been moved from the JSP add-on module
  to the Base module, to fix a problem with ServletContext.getResourcePaths()
  when the JSP module wasn't installed.


Changes in 1.1.1
================

* Fixed auto-discovery of TLDs under WEB-INF so that subdirectories are
  scanned as well.
* Fixed the help messages for JSPC so it includes all supported options
  described in the Reference Manual.
* Added test to prevent a NullPointerException when a TLD under WEB-INF
  doesn't include the <uri> element.
* Upgraded all Tomcat classes to Tomcat 4.1.24, fixing the following
  problems (from the Tomcat release notes; numbers refer to Tomcat bug
  reports):
  + Compiler:
    Added new "fork" option. This tells Ant to fork the JSP page javac
    compile so that it is run in a different JVM from the one Tomcat
    is running in. Please see the JSP Module Reference Manual for more 
    information.
  + #15531
    Background Thread Recompile:
    Fixed a thread synchronization bug which could cause the thread which
    does background JSP recompiles (development=false) to die.
  + JspWriterImpl:
    Remove custom flushing, which caused client disconnects to log
    stack traces with Jasper.
  + #15105
    PageContextImpl:
    pushBody()/popBody() error on tomcat 4.1.X.
  + #15845
    Fixed JSP page compiles so that objects created for performing
    the JSP page compiles which are not reused are dereferenced so
    they are eligible for GC. This should reduce the memory footprint
    and improve GC performance.
  + #16181
    Generator:
    JspWriter not restored properly when exception thrown 
    in a tag's body content.
  + #16200
    Generator:
    Fix isThreadSafe functionality.
  + #16449
    JspServletWrapper:
    Fix race condition in the reloading check by using an object local
    boolean.
  + Generator:
    Added support for <jsp:fallback> to XML syntax.
  + #17049
    Generator:
    Invalid code generated when nesting tags.


Changes in 1.1
==============

* Added support for making JSP tag libraries available for all
  applications by placing the JAR files in the LWS_HOME/shared/lib
  directory. Tag library URIs described by TLDs in META-INF in JAR files
  in this directory are added to the container's map of "well-known URIs",
  see the JSP spec for details. To override a well-known URI, declare the
  tag library in the web.xml file or place the TLD (or a JAR file with
  the TLD) in the appropriate WEB-INF directory.
* Added support for automatic discovery of tag libraries described by
  TLD files placed directly somewhere under WEB-INF (i.e., not in a JAR
  file) as implied by the JSP 1.2 spec and required by the JSP 2.0 spec.


1.0 Release Notes
=================
General
-------
This is the first release of the JSP Add-On Module for LiteWebServer (LWS) 
3.0. This module is based on the Tomcat 4.1.18 JSP container, known as 
Jasper2.

Changes compared to the JSP support in LWS 2.x
----------------------------------------------
* Support for JSP 1.2
* More efficient code generator
* Tag handler instance pooling
* JSP Compiler (JSPC) for precompilation of JSP pages

Known issues
------------
* The LiteXMLParser JAXP parser included with LWS does not support a
  feature used when parsing JSP Documents (JSP files in XML format),
  leading to the loss of XML comments in response generated from the
  JSP Document. Since LiteXMLParser (LXP) is only needed on platforms prior
  to JDK 1.4, you can remove the LXP JAR files if you use a JDK 1.4
  platform to resolve this problem. See the LWS Base Module Reference Manual
  for details.
* The Java compiler leaks memory each time a class is compiled. Web 
  applications containing hundreds of JSP files may as a result trigger 
  out of memory errors once a significant number of pages have been accessed. 
  The memory can only be freed by stopping Tomcat and then restarting it.
  The JSP command line compiler (JSPC) can also be used to precompile the 
  JSPs and avoid this problem. See the JSP Module Reference Manual for
  details.