Spring/spring-webflow
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove OGNL expression support

Browse Source 
Issue: SWF-1694
This commit is contained in:
Rossen Stoyanchev
2017-01-06 16:02:53 -05:00
parent 4fb1b99a8b
commit b263c1c87a
14 changed files with 22 additions and 980 deletions
Download Patch File Download Diff File Expand all files Collapse all files

47
src/reference/el.xml
View File

@@ -79,21 +79,19 @@
<sect2 xml:id="el-spring-el">
<title>Spring EL</title>
<para>
Starting with version 2.1 Web Flow uses the <link xl:href="http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/expressions.html">Spring Expression Language</link> (Spring EL).
Web Flow uses the <link xl:href="http://docs.spring.io/spring/docs/current/spring-framework-reference/html/expressions.html">Spring Expression Language</link> (Spring EL).
Spring EL was created to provide a single, well-supported expression language for use across all the products in the Spring portfolio.
It is distributed as a separate jar <code>org.springframework.expression</code> in the Spring Framework.
Existing applications will need to remove dependencies on <code>org.jboss.el</code> or <code>org.ognl</code> and use <code>org.springframework.expression</code> instead.
See the section below on EL Portability for other notes on upgrading.
</para>
</sect2>
<sect2 xml:id="el-unified-el">
<title>Unified EL</title>
<para>
In Web Flow 2.0 <link xl:href="http://en.wikipedia.org/wiki/Unified_Expression_Language">Unified EL</link> was the default expression language with <code>jboss-el</code> as the implementation.
Use of Unified EL also implies a dependency on <code>el-api</code> although that is typically <emphasis>provided</emphasis> by your web container.
Tomcat 6 includes it, for example.
Spring EL is the default and recommended expression language to use.
However it is possible to replace it with Unified EL if you wish to do so.
Use of <link xl:href="http://en.wikipedia.org/wiki/Unified_Expression_Language">Unified EL</link>
also implies a dependency on <code>el-api</code> although that is typically <emphasis>provided</emphasis>
by your web container.
Although Spring EL is the default and recommended expression language to use,
it is possible to replace it with Unified EL if you wish to do so.
You need the following Spring configuration to plug in the <code>WebFlowELExpressionParser</code> to the <code>flow-builder-services</code>:
<programlisting language="xml"><![CDATA[
<webflow:flow-builder-services expression-parser="expressionParser"/>
@@ -115,35 +113,6 @@
<property name="conversionService" ref="conversionService"/>
</bean>
<bean id="conversionService" class="somepackage.ApplicationConversionService"/>]]>
</programlisting>
</para>
</sect2>
<sect2 xml:id="el-ognl">
<title>OGNL</title>
<note>
<para>
OGNL support is deprecated as of Web Flow version 2.4.
</para>
</note>
<para>
<link xl:href="http://www.ognl.org">OGNL</link> is the third supported expression language.
OGNL is the EL most familiar to Web Flow version 1.0 users.
Please refer to the <link xl:href="http://www.ognl.org/2.6.9/Documentation/html/LanguageGuide/index.html">OGNL language guide</link> for specifics on its EL syntax.
If you wish to use OGNL this is the Spring configuration necessary to plug it in:
<programlisting language="xml"><![CDATA[
<webflow:flow-builder-services expression-parser="expressionParser"/>
<bean id="expressionParser" class="org.springframework.webflow.expression.WebFlowOgnlExpressionParser"/>]]>
</programlisting>
Note that if your application is registering custom converters it's important to ensure the WebFlowOgnlExpressionParser is configured with the conversion service that has those custom converters.
<programlisting language="xml"><![CDATA[
<webflow:flow-builder-services expression-parser="expressionParser" conversion-service="conversionService"/>
<bean id="expressionParser" class="org.springframework.webflow.expression.WebFlowOgnlExpressionParser">
<property name="conversionService" ref="conversionService"/>
</bean>
<bean id="conversionService" class="somepackage.ApplicationConversionService"/>]]>
</programlisting>
</para>
@@ -152,7 +121,7 @@
<sect1 xml:id="el-portability">
<title>EL portability</title>
<para>
In general, you will find Spring EL, Unified EL and OGNL to have a very similar syntax.
In general, you will find Spring EL and Unified EL to have a very similar syntax.
</para>
<para>
Note however there are some advantages to Spring EL.
@@ -160,7 +129,7 @@
Specifically the automatic detection of generic types as well as the use of formatting annotations is currently supported with Spring EL only.
</para>
<para>
There are some minor changes to keep in mind when upgrading to Spring EL from Unified EL or OGNL as follows:
There are some minor changes to keep in mind when upgrading to Spring EL from Unified EL as follows:
<orderedlist>
<listitem><para>Expressions deliniated with <code>${}</code> in flow definitions must be changed to <code>#{}</code>.</para></listitem>
<listitem><para>Expressions testing the current event <code>#{currentEvent == 'submit'}</code> must be changed to <code>#{currentEvent.id == 'submit'}</code>.</para></listitem>

2
src/reference/spring-mvc.xml
View File

@@ -339,7 +339,7 @@ public class BookingFlowHandler extends AbstractFlowHandler {
as a custom MessageCodesResolver. You may also enable data binding use
Spring MVC's native BeanWrapper by setting the
<code>useSpringBinding</code> flag to true. This is an alternative to
using OGNL or the Unified EL for view-to-model data binding. See the
using the Unified EL for view-to-model data binding. See the
JavaDoc API of this class for more information.</para>
</sect1>

2
src/reference/system-setup.xml
View File

@@ -393,7 +393,7 @@ public ViewFactoryCreator viewFactoryCreator() {
<title>expression-parser</title>
<para>
Use the <code>expression-parser</code> attribute to customize the <code>ExpressionParser</code> used by the Web Flow system.
The default ExpressionParser uses the Unified EL if available on the classpath, otherwise OGNL is used.
The default ExpressionParser uses the Unified EL if available on the classpath, otherwise Spring EL is used.
</para>
</sect3>
<sect3 xml:id="builder-service-view-factory-creator">