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)
Use separate API and implementation dependencies for JavaMail. This
paves the way for JavaMail 1.5 where javax.mail:mail is no more.
Exclude the mail dependency from mock-javamail to avoid having multiple
copies on the classpath
Exclude the Geronimo JMS spec from ActiveMQ as the official
java.jms:jms-api artifact is already available
- Updated Java Mail to 1.4.7
- Updated Commons Logging to 1.1.3
- Replaced JMS spec dependency to use the 'official' artifact
- Removed redundant EJB spec dependency
SOAP v1.2 specifies that for SOAP Fault's with Code of "env:Sender" the
HTTP response status code should be 400 (rather than 500 for all other
faults). This commit changes both client and server-side to reflect
this.
Issue: SWS-868
All WS-Addressing EndpointsMappings now support endpoint interceptors
registered via a <sws:interceptors/> block (i.e.
SmartEndpointInteceptors).
Issue: SWS-874
