This is an automated email from the ASF dual-hosted git repository.

robertlazarski pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/axis-axis2-java-core.git

commit b5a2474b8c97ff4b50f0062693f6eb6597728a7c
Author: Robert Lazarski <[email protected]>
AuthorDate: Sat Sep 5 03:51:39 2026 -1000

    Deprecate the mail transport for removal in 2.1.0
    
    SOAP over SMTP was specified and profiled, but a request/response that 
blocks a
    caller thread on a mailbox poll saw very little use even at SOAP's peak. No
    functional change has landed in the module in over a decade; every commit
    touching it since 2015 is a project-wide sweep or a test-dependency bump. 
It is
    enabled by no default axis2.xml, yet axis2-webapp depends on it, so it 
ships to
    everyone regardless. Release note only -- nothing is removed in 2.0.2.
    
    Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
---
 src/site/markdown/release-notes/2.0.2.md | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/src/site/markdown/release-notes/2.0.2.md 
b/src/site/markdown/release-notes/2.0.2.md
index 7bd095e8bd..f9b540e895 100644
--- a/src/site/markdown/release-notes/2.0.2.md
+++ b/src/site/markdown/release-notes/2.0.2.md
@@ -3,6 +3,28 @@ Apache Axis2 2.0.2 Release Notes
 
 (Unreleased)
 
+## Deprecated for Removal
+
+- **The mail transport (`axis2-transport-mail`) is deprecated and is planned 
for
+  removal in 2.1.0.** SOAP over SMTP was specified and profiled, but a 
request/response
+  exchange that blocks a caller thread on a mailbox poll saw very little use 
even when
+  SOAP was at its most popular, and it shows: no functional change has been 
made to
+  this module in over a decade, and every commit touching it since 2015 is 
either a
+  project-wide sweep (the jakarta rename, the SecurityManager removal, a 
package move)
+  or a test-dependency bump.
+
+  It is not enabled by any default `axis2.xml`, but `axis2-webapp` depends on 
it, so
+  the module and its mail provider ship in the WAR and the binary distribution 
to every
+  deployment regardless. Its correlation of responses to requests by 
`In-Reply-To`
+  (`SynchronousCallback` and the callback table in 
`AbstractTransportListener`) is the
+  only such mechanism in the tree and is used by nothing else; the module's 
own source
+  carries long-standing `FIXME` comments saying that machinery does not belong 
where it
+  sits.
+
+  If you use the mail transport, please say so on the dev list -- concrete 
usage is
+  what would keep it. Otherwise plan to move to an HTTP transport before 
2.1.0. Nothing
+  is removed in 2.0.2 and the module continues to work in this release.
+
 ## Security Hardening
 
 Several defaults changed in this release. Each one closes a surface an

Reply via email to