Mojarra 2.2.10 generates responses that begin with an XML declaration: <?xml version='1.0' encoding='utf-8'?> This change broke the expectation in JsfAjaxHandlerTests's testSendAjaxRedirect. The test has been updated to expect the XML declaration. ResourcesBeanDefinitionParserTests has been updated to set up and tear down the mock JDF infrastructure. This ensures that it does not leave any side-effects that cause subsequent tests to fail on some platforms.
Update JsfView so that state saving no longer occurs during processUserEvent(). This is required to ensure that Mojarra's StateContext.release(...) method is not called too early. Prior to Mojarra 2.1.16 multiple calls to saveView had no side effects, but the fix to JAVASERVERFACES-2609 changed this behavior. In order to retain the fix for SWF-1577 the saveState() method is now called from getUserEventState(). This should ensure that the StateContext$AddRemoveListerner is still removed, even when WebFlow bypasses the usual state saving for certain flow redirects. Issue: SWF-1631
This reverts commit d31900e. 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