This reverts commit d31900e5f9.
The fix for SWF-1571 reported against Mojarra 2.1.8 seems to be
problematic when Web Flow's ResponseStateManager is not used as
reported in SWF-1630.
Testing with Mojarra 2.1.20 I can no longer reproduce SWF-1571
and originally it was suspected to be a Mojarra issue. Hence
this revert.
Issue: SWF-1571, SWF-1630
Configure the Spring IO plugin such that it's only applied when the
build is run with -PplatformVersion=<version>. This platformVersion
property is used to determine the version of the Platform that will
be used when running the springIoCheck task. The plugin can be used
by running a build as follows:
./gradlew clean springIoCheck -PplatformVersion=1.0.0.BUILD-SNAPSHOT -PJDK7_HOME=… -PJDK8_HOME=…
This will test the project on JDK7 and JDK 8 using the dependencies
defined in the latest snapshot of Spring IO Platform 1.0.0.
The Spring IO test tasks have been configured to exclude the Tiles 2
tests as Spring IO uses Tiles 3.
The flow-builder-services attribute for specifying a
ValidationHintResolver was originally added to use (incorrectly)
camelback notation, i.e. validationHintResolver. This change fgiixes
that to the XML convention i.e. validation-hint-resolver.
SWF-1629
Before this change, SWF had its own faclets security tag library with
hierarchy root in AbstractAuthorizeTag.
As of this change SWF facelets security tag library inherits Spring SEC
AbstractAuthorizeTag instead, consolidating the two frameworks making
it easier to maintain, extend and reuse. This is made possible by
adding Spring security taglibs module as optional SWF facelets
dependecy. Because the dependency is optional, existing SWF facelets
security tag library users will have to explicitly add Spring Security
taglibs module as dependency.
Issue: SWF-1557
The build now compiles with Servlet API 3.0 and JPA 2.0 both of which
are required with Spring Framework 4.0. However there are no hard
dependencies in Web Flow on either.
Issue: SWF-1600
