You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Mark Roth <ma...@sun.com> on 2002/08/21 07:12:23 UTC

[PATCH] jakarta-tomcat-jasper: PFD features and bugfixes 2

Attached is a second patch to move us towards JSP 2.0 PFD
feature-complete.  More to come in the next few days...

Files Removed (PLEASE REMOVE MANUALLY):
-------------
jasper2/src/share/org/apache/jasper/runtime/ExpressionEvaluatorManager.java


Files Changed (IN PATCH)
-------------
jasper2/src/share/org/apache/jasper/Constants.java
jasper2/src/share/org/apache/jasper/compiler/ErrorDispatcher.java
jasper2/src/share/org/apache/jasper/compiler/Generator.java
jasper2/src/share/org/apache/jasper/compiler/JspUtil.java
jasper2/src/share/org/apache/jasper/compiler/Validator.java
jasper2/src/share/org/apache/jasper/resources/messages.properties
jasper2/src/share/org/apache/jasper/runtime/ExpressionEvaluatorImpl.java
jasper2/src/share/org/apache/jasper/runtime/JspFragmentHelper.java
jasper2/src/share/org/apache/jasper/runtime/JspRuntimeLibrary.java
jasper2/src/share/org/apache/jasper/runtime/PageContextImpl.java


Summary of changes:
    - Removed ExpressionEvaluatorManager
    - Changed EL validation to use
      ExpressionEvaluatorManager.parseExpression
    - PageContextImpl now implements VariableResolver
    - Generated Servlet / Tag Handler now implements FunctionMapper
    - Implemented getExpressionEvaluator() API - Current implementation
      is very inefficient with all sorts of nasty wrappers, but will 
      get much better once the EL evaluator moves into its 
      own subproject.
    - Reworked internal interpreter call to be a proprietary call 
      for the time being, until the EL evaluator moves out of JSTL 
      and into its own project.  Relying on the standard machinery 
      would be too inefficient for the common case.
    - Removed prefix map generation, as it's not being used anywhere.
    - For tag files, moved creation of JspContextWrapper
      to setJspContext.  Now stores both the original and the 
      wrapped JspContext.  Still need to make sure scripting vars 
      are synchronized with the original JspContext.

--
Mark Roth, Java Software
JSP 2.0 Specification Co-Lead
Sun Microsystems, Inc.