The project contains various easy to fix compiler warnings like unused
imports, raw types and no longer needed @SuppressWarnings("unchecked").
This change removes:
* unused imports
* raw types
* no longer needed @SuppressWarnings("unchecked")
Issue: SWS-918
https://jira.spring.io/browse/SWS-918
Spring Security 4.0 removed a number of APIs that were deprecated in
3.x. This commit updates SpringSecurityUtils to avoid using those
APIs. This makes it compatible with Spring Security 4.0 while also
retaining compatibility with Spring Security 3.2.x.
Also, upgrade to Spring Security 3.2.7.RELEASE as the latest point release.
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.
* Created an interface to mark where request and response headers may be accessed
* Updated related classes to use the interface, and in turn, update method visibility
* There are sets of classes aimed at requests and another at repsonses. Have interfaces to serve both, for symmetry.
When configuring max connections for a secured route, the HttpRoute is actually not secured. This causes an improper lookup.
This change updates the test case to ensure several things are verified including the fix provided.
The current code basically assumes that if the payload is a SAXSource,
then it must be backed by a SAX parser. It then passes only the
InputSource to the unmarshaller and ignores the XMLReader. Presumably
this is an optimization because the unmarshaller will likely parse the
XML message in a more efficient way.
This approach causes a problem if the SAXSource is not backed by a
parser but generates the sequence of SAX events using a custom
XMLReader.
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 -PJDK8_HOME=…
This will test the project on JDK 8 using the dependencies defined in
the latest snapshot of Spring IO Platform 1.0.0.
Depend upon ehcache-core rather than ehcache, thereby removing the need
for the exclusion of ehcache-terracotta.
Upgrade to Spring Security 3.2.3 (the 3.2.x line uses ehcache-core)
