org.springframework.web.util Documentation Differences

This file contains all the changes in documentation in the package org.springframework.web.util as colored differences. Deletions are shown like this, and additions are shown like this.

If no deletions or additions are shown in an entry, the HTML tags will be what has changed. The new HTML tags are shown in the differences. If no documentation existed, and then some was added in a later version, this change is noted in the appropriate class pages of differences, but the change is not shown on this page. Only changes in existing text are shown here. Similarly, documentation which was inherited from another class or interface is not shown here.

Note that an HTML error in the new documentation may cause the display of other documentation changes to be presented incorrectly. For instance, failure to close a <code> tag will cause all subsequent paragraphs to be displayed differently.

Convenience methods for accessing JSP 2.0's javax.servlet.jsp.el.ExpressionEvaluator.

The evaluation methods check if the value contains "${" before invoking the EL evaluator, treating the value as "normal" expression (i.e. a literal String value) else.

See .isSpringJspExpressionSupportActive for guidelines on when to use Spring's JSP expression support as opposed to the built-in expression support in JSP 2.0+ containers. @author Juergen Hoeller @author Alef Arendsen @since 11.07.2003 @see javax.servlet.jsp.el.ExpressionEvaluator#evaluateevaluate @deprecated as of Spring 3.2, in favor of the JSP 2.0+ native support for embedded expressions in JSP pages (also applying to tag attributes)

Check whether Spring's JSP expression support is actually active.

Note that JSP 2.0+ containers come with expression support themselves: However, it will only be active for web applications declaring Servlet 2.4 or higher in their web.xml deployment descriptor.

If a web.xml context-param named "springJspExpressionSupport" is found, its boolean value will be taken to decide whether this support is active. If not found, the default is for expression support to be inactive on Servlet 3.0 containers with web applications declaring Servlet 2.4 or higher in their web.xml. For backwards compatibility, Spring's expression support will remain active for applications declaring Servlet 2.3 or earlier. However, on Servlet 2.4/2.5 containers, we can't find out what the application has declared,; so we'll also fall back to keeping expression support active inas such a caseof Spring 3. Recommendations: Explicitly set "springJspExpressionSupport" to "false" in order2, towe preventwon't doubleactivate evaluationSpring's for Servletexpression support 2.4+at basedall applications. then On Servletsince it 3.0got containers,deprecated thisand will be done for you byremoved default byin the framework. If for some reason you nevertheless wantnext Spring's JSP expression support to be active,iteration explicitlyof set the "springJspExpressionSupport" context-param to "true"framework. @param pageContext current JSP PageContext @return true if active (ExpressionEvaluationUtils will actually evaluate expressions); false if not active (ExpressionEvaluationUtils will return given values as-is, relying on the JSP container pre-evaluating values before passing them to JSP tag attributes)