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
The following commit(s) were added to refs/heads/master by this push:
new e8054395fc Fix http:// to https:// for all axis.apache.org site links
e8054395fc is described below
commit e8054395fc14dc9f32bd6292e5181dbaafce0fbd
Author: Robert Lazarski <[email protected]>
AuthorDate: Thu May 14 05:33:21 2026 -1000
Fix http:// to https:// for all axis.apache.org site links
Update 8 links across 6 site source files: Rampart references in
index.xml, modules/index.xml, adv-userguide.xml, and
userguide-forfurtherstudy.xml; banner image/href in site.xml;
core-staging link in release-process.md.
Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
---
src/site/markdown/release-process.md | 2 +-
src/site/site.xml | 22 +++++-----
src/site/xdoc/docs/adv-userguide.xml | 23 +++++-----
src/site/xdoc/docs/http2-integration-guide.xml | 10 ++---
src/site/xdoc/docs/http2-transport-additions.xml | 7 +--
src/site/xdoc/docs/json-streaming-formatter.xml | 50 +++++++++++++++++-----
src/site/xdoc/docs/spring-boot-starter.xml | 30 +++++++------
src/site/xdoc/docs/userguide-forfurtherstudy.xml | 6 +--
.../xdoc/docs/wildfly-http2-integration-guide.xml | 4 +-
src/site/xdoc/index.xml | 8 ++--
src/site/xdoc/modules/index.xml | 6 +--
11 files changed, 100 insertions(+), 68 deletions(-)
diff --git a/src/site/markdown/release-process.md
b/src/site/markdown/release-process.md
index f1a4e9d355..69ffaa2b53 100644
--- a/src/site/markdown/release-process.md
+++ b/src/site/markdown/release-process.md
@@ -218,7 +218,7 @@ If you have multiple keys, you can define a
~/.gnupg/gpg.conf file for a default
* A link to the Nexus staging repository.
* A link to the directory containing the distributions
(<https://dist.apache.org/repos/dist/dev/axis/axis2/java/core/x.y.x/>).
- * A link to the preview of the Maven site
(<http://axis.apache.org/axis2/java/core-staging/>).
+ * A link to the preview of the Maven site
(<https://axis.apache.org/axis2/java/core-staging/>).
If the vote passes, execute the following steps:
diff --git a/src/site/site.xml b/src/site/site.xml
index dba8087d23..df2432d7e6 100644
--- a/src/site/site.xml
+++ b/src/site/site.xml
@@ -8,7 +8,7 @@
~ "License"); you may not use this file except in compliance
~ with the License. You may obtain a copy of the License at
~
- ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~ https://www.apache.org/licenses/LICENSE-2.0
~
~ Unless required by applicable law or agreed to in writing,
~ software distributed under the License is distributed on an
@@ -26,16 +26,16 @@
</skin>
<bannerLeft>
<name>Apache Axis2</name>
- <src>http://www.apache.org/images/asf_logo_wide.png</src>
- <href>http://www.apache.org/</href>
+ <src>https://www.apache.org/images/asf_logo_wide.png</src>
+ <href>https://www.apache.org/</href>
</bannerLeft>
<bannerRight>
- <src>http://axis.apache.org/axis2/java/core/images/axis.jpg</src>
- <href>http://axis.apache.org/axis2/java/core/</href>
+ <src>https://axis.apache.org/axis2/java/core/images/axis.jpg</src>
+ <href>https://axis.apache.org/axis2/java/core/</href>
</bannerRight>
<body>
<breadcrumbs>
- <item name="Apache" href="http://www.apache.org"; />
+ <item name="Apache" href="https://www.apache.org"; />
<item name="Axis2/Java" href="index.html" />
</breadcrumbs>
@@ -79,7 +79,7 @@
<menu name="Resources">
<item name="FAQ" href="faq.html" />
<item name="Articles" href="articles.html" />
- <item name="Wiki"
href="http://wiki.apache.org/ws/FrontPage/Axis2/"; />
+ <item name="Wiki"
href="https://wiki.apache.org/ws/FrontPage/Axis2/"; />
<item name="Reference Library" href="refLib.html" />
<item name="Online Java Docs" href="apidocs/index.html" />
</menu>
@@ -100,10 +100,10 @@
</menu>
<menu name="Apache" inherit="bottom">
<item name="License"
- href="http://www.apache.org/licenses/LICENSE-2.0.html"; />
- <item name="Sponsorship"
href="http://www.apache.org/foundation/sponsorship.html"/>
- <item name="Thanks"
href="http://www.apache.org/foundation/thanks.html"/>
- <item name="Security" href="http://www.apache.org/security/"/>
+ href="https://www.apache.org/licenses/LICENSE-2.0.html"; />
+ <item name="Sponsorship"
href="https://www.apache.org/foundation/sponsorship.html"/>
+ <item name="Thanks"
href="https://www.apache.org/foundation/thanks.html"/>
+ <item name="Security" href="https://www.apache.org/security/"/>
</menu>
</body>
</project>
diff --git a/src/site/xdoc/docs/adv-userguide.xml
b/src/site/xdoc/docs/adv-userguide.xml
index be9d9f1c9e..24d46420b8 100644
--- a/src/site/xdoc/docs/adv-userguide.xml
+++ b/src/site/xdoc/docs/adv-userguide.xml
@@ -7,7 +7,7 @@
~ "License"); you may not use this file except in compliance
~ with the License. You may obtain a copy of the License at
~
- ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~ https://www.apache.org/licenses/LICENSE-2.0
~
~ Unless required by applicable law or agreed to in writing,
~ software distributed under the License is distributed on an
@@ -185,7 +185,7 @@ border="0"/></p>
<p>The service can be deployed by simply dropping the ".aar" file into the
"services" directory in "/webapps/axis2/WEB-INF" of your servlet container.
-We recommend using <a href="http://tomcat.apache.org/";>Apache Tomcat</a> as
+We recommend using <a href="https://tomcat.apache.org/";>Apache Tomcat</a> as
the servlet container. <strong>Please Note that the services directory is
available only after axis2.war has been exploded by Tomcat. However, the
easiest
way to do it is to start Tomcat after axis2.war is copied to the webapps
@@ -415,13 +415,14 @@ the semantics of scope, and how to engage modules in
those scopes.</p>
<p>* If a handler is added to a service or an operation, it will be invoked
for every request received by that service or operation</p>
-<p>Axis2 provides a number of built in Modules (such as <a
-href="">addressing</a>,<a href="">Security</a>, <a href="">WS-Reliable
-Messaging</a>), and they can be engaged as shown above. Please refer to each
-module on how to use and configure them. You can also <a
-href="modules.html">create your own modules with Axis2</a>. Also refer to <a
-href="axis2config.html#Global_Configuration">Axis2 Configuration Guide</a>
-for a reference on the module.xml file.</p>
+<p>Axis2 provides a number of built in Modules (such as
+<a href="../modules/index.html">addressing</a> and
+<a href="https://ws.apache.org/rampart/";>Security (Rampart)</a>),
+and they can be engaged as shown above. Please refer to each
+module on how to use and configure them. You can also
+<a href="../modules/index.html">create your own modules with Axis2</a>.
+Also refer to <a href="axis2config.html#Global_Configuration">Axis2
+Configuration Guide</a> for a reference on the module.xml file.</p>
<h3>WS-Addressing Support</h3>
@@ -457,7 +458,7 @@ transportSender tags to axis2.xml. To learn how to
configure and use
different transports, please refer to the following documents.</p>
<ol>
<li><a href="http-transport.html">HTTP Transports</a></li>
- <li><a href="http://ws.apache.org/commons/transport/";>WS-Commons Transport
project</a></li>
+ <li><a href="https://ws.apache.org/commons/transport/";>WS-Commons Transport
project</a></li>
</ol>
<h3>Attachments</h3>
@@ -470,7 +471,7 @@ information.</p>
<h3>Security</h3>
<p>WS-Security support for Axis2 is provided by <a
-href="http://axis.apache.org/axis2/java/rampart/";>Apache Rampart</a>.</p>
+href="https://axis.apache.org/axis2/java/rampart/";>Apache Rampart</a>.</p>
<h3>REST Web Service</h3>
diff --git a/src/site/xdoc/docs/http2-integration-guide.xml
b/src/site/xdoc/docs/http2-integration-guide.xml
index 87503bdec6..43e852fd3c 100644
--- a/src/site/xdoc/docs/http2-integration-guide.xml
+++ b/src/site/xdoc/docs/http2-integration-guide.xml
@@ -507,15 +507,11 @@ enableALPN = true
(Required for HTTP/2)
<li>Connection efficiency (target: 80% fewer connections via
multiplexing)</li>
</ul>
-<h3>JVM Monitoring Parameters</h3>
-<pre>
--XX:+UseZGC # Low-latency garbage collector
--XX:MaxDirectMemorySize=512m # Direct memory for HTTP/2 buffers
-</pre>
-<p><em>Note:</em> HTTP/2 and streaming are enabled entirely through axis2.xml
+<h3>JVM Parameters</h3>
+<p>HTTP/2 and streaming are enabled entirely through axis2.xml
by selecting the appropriate message receiver and formatter classes (e.g.
<code>EnhancedMoshiJsonFormatter</code>,
<code>MoshiStreamingMessageFormatter</code>).
-No JVM system properties are required.</p>
+No JVM system properties are required for HTTP/2 support.</p>
<h2>Testing Strategy</h2>
diff --git a/src/site/xdoc/docs/http2-transport-additions.xml
b/src/site/xdoc/docs/http2-transport-additions.xml
index 990e974f50..062dc1384a 100644
--- a/src/site/xdoc/docs/http2-transport-additions.xml
+++ b/src/site/xdoc/docs/http2-transport-additions.xml
@@ -299,8 +299,9 @@ compression (HPACK) is always active and requires no Axis2
configuration.</p>
<h3>Memory Management</h3>
<p>Buffer management is handled internally by Apache HttpComponents 5.x.
-The JVM's <code>-XX:MaxDirectMemorySize</code> flag controls the upper bound
-on direct memory used for HTTP/2 I/O buffers.</p>
+The JVM's default direct memory limit (equal to <code>-Xmx</code>) is
+sufficient for most deployments. No additional JVM flags are needed
+for HTTP/2 buffer management.</p>
<h3>Error Handling and Fallback</h3>
@@ -384,7 +385,7 @@ System.setProperty("java.security.properties",
"jdk.tls.alpnCharset=UTF-8");
<h4>Memory Issues with Large Payloads</h4>
<pre>
// Increase heap size for large JSON payloads
--Xmx4g -XX:+UseG1GC -XX:MaxDirectMemorySize=512m
+-Xmx4g -XX:+UseG1GC
</pre>
<h4>Connection Issues</h4>
diff --git a/src/site/xdoc/docs/json-streaming-formatter.xml
b/src/site/xdoc/docs/json-streaming-formatter.xml
index 0d860c79dc..4b4bc00539 100644
--- a/src/site/xdoc/docs/json-streaming-formatter.xml
+++ b/src/site/xdoc/docs/json-streaming-formatter.xml
@@ -50,11 +50,37 @@
during GSON/Moshi serialization. The proxy never sees the full response
body as a single buffer; it forwards chunks as they arrive.</p>
- <p><strong>What this does NOT solve:</strong> Large HTTP
<em>request</em>
- bodies (client to server). If a client sends a very large POST body and
- the proxy rejects it, the fix is client-side: break the request into
- smaller payloads (for example, date-range chunking) or add a pre-send
- size guard. The streaming formatter operates on the response path
only.</p>
+ <p><strong>Request path (client to server):</strong> The streaming
+ formatter operates on the <em>response</em> path only. For large
+ HTTP POST request bodies, note that neither
+ <a href="https://www.rfc-editor.org/rfc/rfc9110#section-8.6";>HTTP/1.1
(RFC 9110)</a>
+ nor <a href="https://www.rfc-editor.org/rfc/rfc9113";>HTTP/2 (RFC
9113)</a>
+ define a limit on request body size. HTTP/2 is actually better
+ suited for large requests because the body is sent as DATA frames
+ with flow control — the sender and receiver negotiate how much
+ data to send at a time, preventing buffer overflow. In practice,
+ size rejections come from infrastructure layers, not the HTTP
+ spec:</p>
+
+ <ul>
+ <li><strong>Reverse proxies</strong> (CloudFlare, nginx) —
+ <code>client_max_body_size</code> or equivalent; increase
+ or remove the limit</li>
+ <li><strong>Load balancers</strong> (AWS ALB/NLB) — ALB imposes
+ no body size limit when routing to EC2/ECS targets.
+ The 1MB limit applies only to the ALB→Lambda integration
+ path (an AWS hard limit that cannot be increased).
+ NLB operates at TCP level and has no body size limit</li>
+ <li><strong>Web servers</strong> (Tomcat, WildFly) —
+ <code>maxPostSize</code> / <code>max-post-size</code>;
+ set to <code>-1</code> for unlimited</li>
+ </ul>
+
+ <p>When a large POST is rejected, debug the specific error and
+ the infrastructure layer that imposed the limit — the fix is
+ usually a configuration change, not a code refactor. Breaking
+ requests into smaller payloads is a last resort when the
+ infrastructure limit cannot be changed.</p>
</section>
<section name="Available Variants">
@@ -259,12 +285,14 @@ OutputStream flushingStream = new
FlushingOutputStream(outputStream, flushInterv
</section>
<section name="Axis2/C Equivalent">
- <p>The same pattern applies to Axis2/C services using Apache httpd
- with mod_axis2. During JSON response generation, call
- <code>ap_rflush(r)</code> periodically to flush the response
- bucket brigade. This causes mod_h2 to emit HTTP/2 DATA frames
- incrementally, achieving the same proxy-friendly streaming behavior
- as the Java formatter.</p>
+ <p><a href="https://axis.apache.org/axis2/c/core/";>Axis2/C</a>
+ achieves the same streaming behavior natively through Apache httpd's
+ <code>mod_h2</code>. During JSON response generation, the C service
+ calls <code>ap_rflush(r)</code> periodically to flush the response
+ bucket brigade. This causes <code>mod_h2</code> to emit HTTP/2 DATA
+ frames incrementally — the same 64KB chunked pattern as the Java
+ formatter, with identical proxy behavior. Both implementations
+ produce matching HTTP/2 frame sequences for the same payload.</p>
</section>
</body>
diff --git a/src/site/xdoc/docs/spring-boot-starter.xml
b/src/site/xdoc/docs/spring-boot-starter.xml
index a416271fde..e7eecba264 100644
--- a/src/site/xdoc/docs/spring-boot-starter.xml
+++ b/src/site/xdoc/docs/spring-boot-starter.xml
@@ -44,32 +44,38 @@ with sensible defaults — for both SOAP and JSON-RPC
services.</p>
<li><strong>Native HTTP/2 with backpressure</strong> — the
<a href="http2-transport-additions.html">H2TransportSender</a>
provides connection multiplexing, flow control, and ALPN negotiation
- as a drop-in transport layer.</li>
+ as a drop-in transport layer. See also the
+ <a href="http2-integration-guide.html">HTTP/2 overview</a>.</li>
<li><strong>AI-ready services (MCP)</strong> — Axis2 auto-generates an
<a href="json-rpc-mcp-guide.html">MCP tool catalog</a> from deployed
services. AI assistants discover and call your services as tools
- without hand-authored definitions.</li>
+ without hand-authored definitions. See
+ <a href="mcp-examples.html">MCP examples</a> for live demos.</li>
<li><strong>Response field selection</strong> — the
<a
href="json-streaming-formatter.html#Field_Selection"><code>?fields=</code></a>
query parameter lets clients request only the fields they need,
- reducing payload size and AI token consumption at the serialization
- layer with zero application code.</li>
+ reducing payload size and AI token consumption at the
+ <a href="json-streaming-formatter.html">serialization layer</a>
+ with zero application code.</li>
<li><strong>OpenAPI schemas from Hibernate mappings</strong> — the
<a href="openapi-jpa-schema.html">JPA/Hibernate schema generator</a>
produces read and write JSON Schemas directly from
- <code>@Entity</code> annotations or <code>.hbm.xml</code> files.
- No hand-authored API contracts — the schema stays in sync with
- the database model by construction.</li>
+ <code>@Entity</code> annotations or <code>.hbm.xml</code> files,
+ including a <a href="openapi-jpa-schema.html#batch_generation">batch CLI
tool</a>
+ for large codebases. No hand-authored API contracts — the schema stays
+ in sync with the database model by construction.</li>
<li><strong>Built-in pagination</strong> — the
<a href="json-pagination.html"><code>PaginatedResponse</code></a>
- wrapper provides offset/limit pagination with server-enforced
- safety limits, <code>totalCount</code> for page controls, and
- <code>hasMore</code> for infinite scroll — mapping directly to
+ wrapper provides offset/limit pagination with
+ <a href="json-pagination.html#safety">server-enforced safety limits</a>,
+ <code>totalCount</code> for
+ <a href="json-pagination.html#frontend_patterns">page controls</a>,
+ and <code>hasMore</code> for infinite scroll — mapping directly to
JPA/Hibernate's
<code>setFirstResult</code>/<code>setMaxResults</code>.</li>
<li><strong>SOAP + JSON from the same services</strong> — serve both
SOAP/XML and JSON-RPC from the same Spring beans, selected by
- configuration. Useful for enterprises maintaining both legacy
- and modern clients.</li>
+ <a href="#soap_vs_json">configuration</a>. Useful for enterprises
+ maintaining both legacy and modern clients.</li>
</ul>
<p>This starter supports both <strong>WAR deployment</strong> to an external
container
diff --git a/src/site/xdoc/docs/userguide-forfurtherstudy.xml
b/src/site/xdoc/docs/userguide-forfurtherstudy.xml
index be486d97fd..566ebdf278 100644
--- a/src/site/xdoc/docs/userguide-forfurtherstudy.xml
+++ b/src/site/xdoc/docs/userguide-forfurtherstudy.xml
@@ -7,7 +7,7 @@
~ "License"); you may not use this file except in compliance
~ with the License. You may obtain a copy of the License at
~
- ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~ https://www.apache.org/licenses/LICENSE-2.0
~
~ Unless required by applicable law or agreed to in writing,
~ software distributed under the License is distributed on an
@@ -97,11 +97,11 @@ Study</strong></a></li>
</ul>-->
<h2>Resources</h2>
<p><a href="Axis2ArchitectureGuide.html">Axis2 Architecture</a></p>
-<p><a href="http://ws.apache.org/axiom/userguide/userguide.html";>Axiom User
Guide</a></p>
+<p><a href="https://ws.apache.org/axiom/userguide/userguide.html";>Axiom User
Guide</a></p>
<p><a href="rest-ws.html">RESTful Web Services</a></p>
<p><a href="http-transport.html">HTTP Transports</a></p>
<p><a href="mtom-guide.html">MTOM with Axis2</a></p>
-<p><a href="http://axis.apache.org/axis2/java/rampart/";>Securing SOAP Messages
with Apache Rampart</a></p>
+<p><a href="https://axis.apache.org/axis2/java/rampart/";>Securing SOAP
Messages with Apache Rampart</a></p>
<p><a href="soapmonitor-module.html">SOAPMonitor</a></p>
<p><a href="adv-userguide.html">Apache Axis2 Advance User's Guide</a></p>
</body>
diff --git a/src/site/xdoc/docs/wildfly-http2-integration-guide.xml
b/src/site/xdoc/docs/wildfly-http2-integration-guide.xml
index 17a0b88428..263a70b90c 100644
--- a/src/site/xdoc/docs/wildfly-http2-integration-guide.xml
+++ b/src/site/xdoc/docs/wildfly-http2-integration-guide.xml
@@ -221,8 +221,8 @@ depend on payload size, network conditions, and JVM
configuration):</em>
<tr>
<td><strong>Memory Optimization</strong></td>
<td><code>http2-header-table-size="4096"</code></td>
- <td>(JVM <code>-XX:MaxDirectMemorySize</code>)</td>
- <td>✅ Conservative header caching; JVM direct memory controls HTTP/2
buffer limits</td>
+ <td>(JVM default is sufficient)</td>
+ <td>✅ Conservative header caching; JVM default direct memory limit is
adequate</td>
</tr>
<tr>
<td><strong>Push Disabled</strong></td>
diff --git a/src/site/xdoc/index.xml b/src/site/xdoc/index.xml
index 44e9949b85..bd9a3d9059 100644
--- a/src/site/xdoc/index.xml
+++ b/src/site/xdoc/index.xml
@@ -7,7 +7,7 @@
~ "License"); you may not use this file except in compliance
~ with the License. You may obtain a copy of the License at
~
- ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~ https://www.apache.org/licenses/LICENSE-2.0
~
~ Unless required by applicable law or agreed to in writing,
~ software distributed under the License is distributed on an
@@ -26,7 +26,7 @@
<h1>Welcome to Apache Axis2/Java</h1>
<p>Apache Axis2™ is a Web Services JSON / SOAP / WSDL engine, the
successor to the
widely used <a href=
-"http://ws.apache.org/axis/";>Apache Axis</a> SOAP stack. Axis2 serves
+"https://ws.apache.org/axis/";>Apache Axis</a> SOAP stack. Axis2 serves
the same business logic through multiple protocols simultaneously —
JSON-RPC, REST, and <a href="docs/mcp-architecture.html">MCP (Model Context
Protocol)</a>
— from a single service deployment.
@@ -55,7 +55,7 @@ so legacy SOAP services with WS-Security policies can run
unchanged on
the same Tomcat 11 / WildFly 32 / WildFly 39 stack as the rest of
Axis2/Java. Minimum OpenJDK version is 17; tested with the same
server/JDK combinations listed below. See the
-<a href="http://axis.apache.org/axis2/java/rampart/";>Apache Rampart
+<a href="https://axis.apache.org/axis2/java/rampart/";>Apache Rampart
site</a> for details.</p>
<p>Apache Axis2, Axis2, Apache, the Apache feather logo, and the Apache Axis2
project logo are trademarks of The Apache Software Foundation.</p>
<h3><em>Why Apache Axis2 in 2026:</em></h3>
@@ -91,7 +91,7 @@ serialization layer with zero overhead when unused. Most
frameworks treat
HTTP/2 as a transparent container feature; Axis2 integrates it into the
message formatter.
Legacy SOAP services continue to work unchanged — the SOAP handler
chain,
-WS-Security (<a href="http://axis.apache.org/axis2/java/rampart/";>Apache
Rampart</a>),
+WS-Security (<a href="https://axis.apache.org/axis2/java/rampart/";>Apache
Rampart</a>),
and WS-Addressing are fully supported.</p>
<p>Axis2 comes with many new features, enhancements and industry
specification implementations. The key features offered are as
diff --git a/src/site/xdoc/modules/index.xml b/src/site/xdoc/modules/index.xml
index ad02fdb645..46b723f7f6 100644
--- a/src/site/xdoc/modules/index.xml
+++ b/src/site/xdoc/modules/index.xml
@@ -8,7 +8,7 @@
~ "License"); you may not use this file except in compliance
~ with the License. You may obtain a copy of the License at
~
- ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~ https://www.apache.org/licenses/LICENSE-2.0
~
~ Unless required by applicable law or agreed to in writing,
~ software distributed under the License is distributed on an
@@ -44,11 +44,11 @@ Axis2.</p>
</tr>
<!-- SOAPMonitor removed: AXIS2-6105 -->
<tr>
-<td><a href="http://ws.apache.org/rampart/";>Rampart</a></td>
+<td><a href="https://ws.apache.org/rampart/";>Rampart</a></td>
<td>The WS-Security and WS-SecureConversation implementation for
axis2. Now with a new configuration model based on
WS-SecurityPolicy</td>
-<td><a
href="http://axis.apache.org/axis2/java/rampart/";>http://axis.apache.org/axis2/java/rampart/</a></td>
+<td><a
href="https://axis.apache.org/axis2/java/rampart/";>https://axis.apache.org/axis2/java/rampart/</a></td>
</tr>
</tbody>
</table>
