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
AP: fix springbootdemo WildFly build and clarify Tomcat vs WildFly docs
- Update springbootdemo/pom.xml Axis2 versions 2.0.0-SNAPSHOT -> 2.0.1-SNAPSHOT
so local Maven install resolves correctly
- Fix Tomcat11 guide: context root is / (ROOT deployment), not /axis2-json-api;
correct all curl example URLs accordingly
- Replace 2-item differences list with a full comparison table in Tomcat11 guide
covering: context root, deploy method, WildFly-specific files, DataSource
auto-config exclusion, HTTP/2 config, and JSON format
- Add concise WildFly vs Tomcat differences summary in WildFly guide with link
to Tomcat11 guide
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The key differences between the two deployments are:
139
142
</p>
143
+
<ul>
144
+
<li><strong>Context root:</strong> On WildFly the WAR name becomes the context root (<code>/axis2-json-api</code>);
145
+
on Tomcat 11 (ROOT deployment) the context root is <code>/</code> and service URLs omit the <code>/axis2-json-api</code> prefix.</li>
146
+
<li><strong>Deploy trigger:</strong> WildFly requires a <code>.dodeploy</code> marker file; Tomcat uses <code>cp -r</code> to <code>webapps/ROOT/</code>.</li>
147
+
<li><strong>WildFly-specific files:</strong> <code>jboss-deployment-structure.xml</code> and <code>jboss-web.xml</code> are required here but absent from the Tomcat variant.</li>
148
+
<li><strong>DataSource auto-config:</strong> WildFly suppresses Spring Boot's DataSource auto-configuration automatically;
149
+
Tomcat requires explicit exclusion in <code>@SpringBootApplication</code>.</li>
150
+
<li><strong>JSON request format:</strong> Identical for both — <code>{"methodName":[{"paramName":{...}}]}</code>.</li>
151
+
</ul>
140
152
<p>Please deploy the result of the maven build via 'mvn clean install', axis2-json-api.war, into your servlet container and ensure that it installs without any errors.</p>
0 commit comments