You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/site/markdown/release-notes/2.0.0.md
+95-2Lines changed: 95 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,8 @@ and Wildfly 32 and above, and is expected to support EE 10 and Spring 6 / Spring
6
6
7
7
The Axis2 project transition to jakarta depends partly on Axiom, which has also been updated to 2.0.0.
8
8
9
+
Axis2 added two committers recently and after this big jakarta update that changed nearly every file and dependency of the project, the community can once again expect releases several times a year to fix bugs and update dependencies with CVE's.
10
+
9
11
The JSON support has been updated with many bugs fixed, while the examples have
10
12
been updated to use Spring Boot 3. Axis2 isn't just for SOAP anymore, as some committers currently only use JSON in their own projects and not SOAP at all.
11
13
@@ -31,6 +33,97 @@ OSGI support is also missing. The state of its dependency Felix and jakarta is u
31
33
32
34
The Code generator plugin for Eclipse is broken. The docs as well as the code are outdated. If interested in contributing a fix, see Jira issue AXIS2-5955.
33
35
34
-
For those interested in Rampart - an optional implementation of WS-Sec* standards that depends on Axis2 - they can expect a Rampart 2.0.0 soon that isn't expected to add much to the recently released Rampart 1.8.0 - a release that is based on the previous Axis2 version, 1.8.2. Mostly that Rampart 2.0.0 release will upgrade OpenSAML to 5.x so that it supports jakarta, while the remaining deps that need updates are few.
36
+
For those interested in Rampart - an optional implementation of WS-Sec* standards that depends on Axis2 - they can expect a Rampart 2.0.0 soon that isn't expected to add much to the recently released Rampart 1.8.0, a release that is based on the previous Axis2 version 1.8.2. Mostly, the upcoming Rampart 2.0.0 release will upgrade OpenSAML to 5.x so that it supports jakarta, while the remaining deps that need updates are few.
35
37
36
-
Axis2 added two committers recently and after this big jakarta update that changed nearly every file and dependency of the project, the community can once again expect releases several times a year to fix bugs and update dependencies with CVE's.
38
+
Apache Axis2 2.0.0 Jira issues fixed
39
+
------------------------------------
40
+
41
+
<h2> Bug
42
+
</h2>
43
+
<ul>
44
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-5689'>AXIS2-5689</a>] - A Veracode security scan reports multiple severity 4 security flaws in axis2.jar
45
+
</li>
46
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-5900'>AXIS2-5900</a>] - If and else branches has the same condition
47
+
</li>
48
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-5901'>AXIS2-5901</a>] - Redundant conditions in an if statement
49
+
</li>
50
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-5948'>AXIS2-5948</a>] - Proxy settings ignored if username not specified
51
+
</li>
52
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-5964'>AXIS2-5964</a>] - AbstractJSONMessageFormatter NOT using CharSetEncoding when reding Json string Bytes
53
+
</li>
54
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-5971'>AXIS2-5971</a>] - AxisServlet.processURLRequest use content-type header instead of accept
55
+
</li>
56
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6030'>AXIS2-6030</a>] - Axis2 connections are not returned to connection pool on 1.8.0 with JAXWS
57
+
</li>
58
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6035'>AXIS2-6035</a>] - Axis2 libraries not compatible with Tomcat 10
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6041'>AXIS2-6041</a>] - totalDigits Facet of XSD type short incorrectly treated in databinding
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6043'>AXIS2-6043</a>] - StackOverflowError in org.apache.axis2.client.Options.getSoapVersionURI()
67
+
</li>
68
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6044'>AXIS2-6044</a>] - HTTPProxyConfigurator system property takes precedence over axis configuration and message context proxy properties
69
+
</li>
70
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6045'>AXIS2-6045</a>] - NPE after upgrade to 1.8.2
71
+
</li>
72
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6046'>AXIS2-6046</a>] - AxisFault after upgrade to 1.8.0
73
+
</li>
74
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6050'>AXIS2-6050</a>] - Latest Axis2 1.8.2 release not compatible with Glassfish6/J2EE9
75
+
</li>
76
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6057'>AXIS2-6057</a>] - Special characters are not allowed in password after upgrade( from 1.7.9 to 1.8.2)
77
+
</li>
78
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6062'>AXIS2-6062</a>] - Is such a flexibility necessary allowing LDAP (and RMI, JRMP, etc.) protocol in `JMSSender`?
79
+
</li>
80
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6063'>AXIS2-6063</a>] - Add enableJSONOnly parameter to axis2.xml
81
+
</li>
82
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6064'>AXIS2-6064</a>] - CVE associtate with dependency jars of axis2
83
+
</li>
84
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6065'>AXIS2-6065</a>] - Small problem with incorrect log output in AxisServlet#processAxisFault
85
+
</li>
86
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6066'>AXIS2-6066</a>] - Site generation/deployment is broken
87
+
</li>
88
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6067'>AXIS2-6067</a>] - CVE with dependency jars of axis2
89
+
</li>
90
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6068'>AXIS2-6068</a>] - ConverterUtilTest is locale-dependent
91
+
</li>
92
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6073'>AXIS2-6073</a>] - Axis2 httpclient5 RequstImpl doesnt initialize version & protocol with https
93
+
</li>
94
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6075'>AXIS2-6075</a>] - axis2-wsdl2code-maven-plugin documentation is stuck on version 1.7.9
95
+
</li>
96
+
</ul>
97
+
98
+
<h2> Improvement
99
+
</h2>
100
+
<ul>
101
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-5975'>AXIS2-5975</a>] - More specific Runtime Exceptions instead of just "Input values do not follow defined XSD restrictions"
102
+
</li>
103
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6049'>AXIS2-6049</a>] - Generated Exceptions differ each generation
104
+
</li>
105
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6054'>AXIS2-6054</a>] - when an inexistent enum value arrives, do not just throw an IllegalArgumentException without any exception
106
+
</li>
107
+
<li>[<ahref='https://issues.apache.org/jira/browse/AXIS2-6059'>AXIS2-6059</a>] - Improve logging by default
0 commit comments