* Move baseline from Spring 4.2.7.RELEASE to 4.2.8.RELEASE
* Add CircleCI for building pull requests against baseline Spring, Spring4-next, and Spring5
* Make it possible to run the build with different dependencies and different version of JDK
* Fix JUnit to make it forward compatible
* Fix other things that are deprecated in Spring 4.3 and removed in Spring 5
This commit introduces a ClientInterceptorAdapter with a default implementation
of the methods and providing a protected Log instance for subclasses. This convenience
class allows for pre-/post only ClientInterceptor instances without having to
add empty methods to it.
The getName() method in JaxbStreamingPayload doesn't report the actual
namespace prefix that is later generated by the writeTo method. With
Axiom 1.2.13 that didn't cause problems, but 1.2.14 is less lenient,
causing an error as described in AXIOM-463.
This change:
* Updates the StreamingPayload documentation to specify that the
namespace prefix in the QName returned by getName() has no significance
(which is effectively how things are currently).
* Updates AxiomSoapBody so that it Axiom is aware that the namespace
prefix of the created OMSourcedElement is unknown.
* Modifies the unit test for setStreamingPayload so that it uses a
StreamingPayload with a prefix mismatch.
Correction for multiple keys with different values in HTTP Response.
Before, in response of mimeheader:
- cookie: value2
- cookie: value2
Now :
- cookie: value1
- cookie: value2
Issue: SWS-924
More recent versions of HTTP components normalise an HTTPHost when it’s
used to create an HTTPRoute. As part of this normalization the host’s
port is set to the default port for the host’s scheme, e.g. an https
scheme will result in a port of 443 and an http scheme will result in
a port of 80
This commit updates the tests so that they will accept the behaviour
of HTTP Components 4.3.x (the port is -1) and HTTP Components 4.5.x
(the port is 80 for http and 443 for https). Compatibility with HTTP
Components 4.5.x allows Spring Web Services’ tests to pass when
they’re run as part of the Spring IO Platform 2.0 release process
which uses a more recent version of HTTP components than the default
Spring Web Services build.
