Skip to content

Commit 9367f45

Browse files
committed
1 parent 4e61e1a commit 9367f45

File tree

2 files changed

+73
-0
lines changed

2 files changed

+73
-0
lines changed

changelog.txt

Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
SPRING WEB SERVICES CHANGELOG
2+
=============================
3+
http://www.springframework.org/spring-ws
4+
5+
Changes in version 1.5.0 Milestone 2
6+
-------------------------
7+
8+
** Bug
9+
* [SWS-257] - Infinite loop in XsdBasedSoap11Wsdl4jDefinitionBuilder#buildMessages method
10+
* [SWS-258] - getting error when trying to use IBM MQ JMS implementation as transport.
11+
* [SWS-264] - XPathExpressionFactory should fallback to Jaxen if no JAXP 1.3 XPath implementation is available
12+
* [SWS-265] - AbstractStaxXmlReader should support the required standard SAX features (namespace, namespace-prefixes...)
13+
* [SWS-266] - AxiomContentHandler should empty the response body before adding the transformation result
14+
* [SWS-267] - code bugs in Reference docs section 4.3.1
15+
* [SWS-268] - cope typos in reference docs section 6.2.4 and 6.2.5
16+
* [SWS-274] - Soap headers with whitespace cause java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.impl.TextImpl - Part II
17+
* [SWS-275] - NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.
18+
* [SWS-276] - PayloadTransformingInterceptor has a typo in the example
19+
20+
** Improvement
21+
* [SWS-92] - JAXP 1.4 support
22+
* [SWS-148] - WebServiceTemplte needs two more methods in order to easy enable ws security client support
23+
* [SWS-231] - @Endpoint component scanning
24+
* [SWS-243] - AxiomSoapHeaderElement has no convenient way to access child elements of the header element
25+
* [SWS-246] - Better support for large Axiom attachments
26+
* [SWS-251] - Improve OSGi manifest
27+
* [SWS-253] - Tiger jars should not include non-tiger classes
28+
* [SWS-255] - Support for javax.jms.TextMessage
29+
* [SWS-261] - There are more default HandlerAdapters in Spring-MVC
30+
* [SWS-262] - Endpoint annotation should be annotated as @Inherited
31+
* [SWS-269] - OSGi bundleSymName
32+
* [SWS-270] - Changes for WS XSD for tooling
33+
* [SWS-272] - Add removeHeaderElement(QName) to SoapHeader
34+
* [SWS-278] - Add traffic logging when response is fault
35+
36+
** New Feature
37+
* [SWS-143] - Client-side WS-Security support
38+
* [SWS-194] - Add Interceptor functionality to WebServiceTemplate
39+
* [SWS-207] - WSS4J-based WS-Security implementation
40+
* [SWS-277] - URI-based routing
41+
* [SWS-279] - AcegiUsernamePasswordCallbackHandler
42+

notes.txt

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
I'm pleased to announce that Spring Web Services 1.5.0 M2 has been released! This milestone release introduces:
2+
3+
* WSS4J-based WS-Security implementation, which allows for WS-Security on non-SUN JDKs (i.e. WebSphere) and JDK 1.4
4+
* Client-side interception mechanism, including support for WS-Security
5+
* URI-based routing
6+
* @Endpoints are now @Components, so they are automatically picked up when using Spring 2.5 component scanning
7+
* The JMS support now supports TextMessages, in addition to the BytesMessages introduced in 1.5.0 M1.
8+
9+
Additionally, there are other minor improvements and bug fixes.
10+
11+
Spring-WS 1.5.0 M2 is the second milestone in the 1.5 series, which - in addition to the aforementioned features - will
12+
include support for WS-Addressing. The 1.5.0 series is 95% backwards compatible, though support for Java 1.3 has been
13+
dropped, in favor of Java 1.6. As of this milestone, Spring-WS requires Java 6 to build.
14+
15+
The next release in this branch will will be 1.5.0 Release Candidate 1, to be released around the 29th of February,
16+
After 1.5.0 final has been release, there will be a 1.0.4, backporting all bugfixes in the 1.5 branch.
17+
18+
For Maven users, please note that this release is not published at the central maven repository. Instead it is
19+
published on Amazon's S3 service, like all Spring milestones. To use it, add the following repository to your POM:
20+
21+
<repository>
22+
<id>spring-milestone</id>
23+
<name>Spring Milestone Repository</name>
24+
<url>http://s3.amazonaws.com/maven.springframework.org/milestone</url>
25+
</repository>
26+
27+
For more information, see http://static.springframework.org/spring-ws/sites/1.5/
28+
29+
Cheers,
30+
31+
Arjen

0 commit comments

Comments
 (0)