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 bb669464b54da44bdc3677dc9bc663b75433320f Author: Robert Lazarski <[email protected]> AuthorDate: Thu Oct 29 04:34:51 2026 -1000 Note the JSON dispatcher content-dispatch change in 2.0.3 release notes Co-Authored-By: Claude Opus 5.5 <[email protected]> --- src/site/markdown/release-notes/2.0.3.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/src/site/markdown/release-notes/2.0.3.md b/src/site/markdown/release-notes/2.0.3.md index 29b3735720..5dc77fff7f 100644 --- a/src/site/markdown/release-notes/2.0.3.md +++ b/src/site/markdown/release-notes/2.0.3.md @@ -2,3 +2,18 @@ Apache Axis2 2.0.3 Release Notes -------------------------------- (Unreleased) + +## Upgrading from 2.0.2 + +| Change | Restore the old behaviour with | +|---|---| +| The JSON dispatcher no longer selects a service from the XML body namespace | `<parameter name="allowContentBasedServiceDispatch">true</parameter>` | + +`JSONBasedDefaultDispatcher`, the Dispatch-phase dispatcher in the Spring Boot +starter's `axis2-json.xml`, now honours `allowContentBasedServiceDispatch` as the +SOAP body dispatchers have since 2.0.2. JSON-RPC requests are unaffected, since their +service comes from the request URI. A deployment that posted `application/xml` to a +URI naming no service, relying on the root element's namespace to pick the service, +now gets a service-not-found fault until the parameter is set. Set it only if +services are genuinely addressed that way, and not alongside per-service security +modules.
