For cases where isMyFacesInUse cannot properly detect due to issues in
dependent libraries (e.g. Tomahawk) we also check if Mojarra is
even present to strengthen those checks.
Issue: SWF-1687
While the methods manipulating or accessing the list are synchronized,
the ConversationContainer class is also subject to serialization.
Issue: SWF-1668
The JSF com.sun.faces.facelets.tag.jsf.ComponentSupport in 2.2.7
started using FacesContext#isPostBack to check if a new component
tree is being built prior to attempting to find a child component.
In Web Flow where we redirect prior to rendering, and hence lose
the value of isPostback (because ResponseStateManagerImpl no longer
finds the parameter with the view state), it causes components to
be re-created and lose their local values.
This change overrides isPostback in FlowFacesContext in order to
return true in cases where the UIViewRoot has been restored from
flash scope and is fully built.
Issue: SWF-1645
Spring Framework 4.2 removes the queryForInt method on JdbcTemplate in
favour of queryForObject which is also available in earlier versions.
This commit replaces calls to queryForInt with queryForObject, thereby
allowing the tests to be run against Spring Framework 4.1 (the default)
and Spring Framework 4.2 (for Spring IO Platform 2.0 compatibility
testing).
Spring IO Platform 2.0 will remove the managed versions .properties
file as support for it has been removed in Spring Boot 1.3.
This commit moves the build onto a new version of the Spring IO Plugin
that uses the Maven bom rather than the properties file.
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.
