Talk:Apache Axis2

Fair use rationale for Image:Apache Axis2 Logo.jpg

Image:Apache Axis2 Logo.jpg is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.

Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Wikipedia:Fair use rationale guideline is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.

If there is other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page. Note that any fair use images uploaded after 4 May, 2006, and lacking such an explanation will be deleted one week after they have been uploaded, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.

BetacommandBot 04:51, 27 October 2007 (UTC)

Request edit: stale release data, stale reference URLs, and the Java/C distinction

Conflict of interest disclosure: I am a committer on Apache Axis2. Nothing below is promotional or evaluative. Each item is a factual correction, kept small enough that a reviewer can verify it against a cited source. I am posting here rather than editing directly because of the COI.

The article carries an {{update}} banner (last update 2 April 2026). I believe items 1–3 are the substance of what it is asking for.

1. The infobox gives one release for two separately-released implementations

The infobox lists a single "Stable release 2.0.0 (4 March 2025)" for a project the article correctly describes as written in "C and Java". That figure is not invented — it is the Axis2/Java 2.0.0 release, which Maven Central records as published on 5 March 2025. The problem is that one implementation's release is presented as the whole project's. The two are released independently, on separate version lines, so no single version or date applies to both. Both have also had newer releases since.

Proposed: replace the single |latest release version= with one entry per implementation.

• Axis2/Java — 2.0.1 (17 May 2026)
• Axis2/C — 2.0.0 (27 April 2026)

Sources:

• Axis2/Java 2.0.1 — Maven Central records org.apache.axis2:axis2:2.0.1

 as published 17 May 2026
 (https://central.sonatype.com/artifact/org.apache.axis2/axis2/2.0.1).

• Axis2/C 2.0.0 — the signed source release, its signature and its checksum are

 dated 27 April 2026 in the ASF distribution archive
 (https://archive.apache.org/dist/axis/axis2/c/core/2.0.0/).

A note on why these dates and not others, since a reviewer may find figures that disagree. I have dated each release by when its artifacts were published, which is verifiable from the two links above. Version-control tag dates differ from these and are not release dates — for Axis2/C the tagged commit is 3 April 2026 and the tag itself was created 27 April 2026. The announcement emails for both releases went out later still, in late May 2026, for reasons unrelated to when the software shipped. If a reviewer prefers a different convention I am happy to follow it; I have used artifact publication because it is the one a reader can check.

2. The article does not distinguish how the two implementations deploy

This is the change most useful to a reader. The article currently says Axis2 "provides the capability to add Web services interfaces to Web applications" and "can also function as a standalone application server", without indicating which implementation does which. As written the two look interchangeable, and their deployment models are entirely different.

Proposed addition to the body:

Axis2/Java deploys as a web application into a servlet container, and provides

modules for integration with the Spring Framework. Axis2/C is a native library

that runs as a module inside the Apache HTTP Server, as a standalone server, or

linked directly into an application.

Source: the documentation for each implementation on axis.apache.org. The Spring integration modules are part of the Axis2/Java source tree.

3. The feature list omits JSON and HTTP/2

The existing list already includes "integrated REST support". JSON and HTTP/2 are the same kind of plain capability statement and are currently absent.

Proposed additions to the existing feature list:

• JSON, in addition to SOAP and REST
• HTTP/2 as a transport

Source: the release notes on axis.apache.org. Please cite the specific release that introduced each rather than a general documentation page.

4. Two reference URLs are stale

Neither of these is a content change; both are link maintenance.

• The source-repository link points to

 https://svn.apache.org/repos/asf/axis/axis2/java/core/trunk/.
 Development moved to Git; the repository is now at
 https://github.com/apache/axis-axis2-java-core (ASF canonical
 remote: gitbox.apache.org).

• The modules reference points to

 https://ws.apache.org/axis2/modules/index.html, which now returns
 a 301 redirect to
 https://axis.apache.org/axis2/java/core/modules/index.html. The
 citation should be updated to the current URL.

5. The module list is not supported by the source it cites

I want to be careful how I put this, because module maintenance status is exactly the kind of thing a committer should not be asserting from personal knowledge. So this item rests only on the article's own citation.

The article lists Sandesha and Kandula among Axis2's modules, citing the Axis2 modules page. That page — reached by following the article's own reference, which 301-redirects to https://axis.apache.org/axis2/java/core/modules/index.html — now lists two modules: Addressing and Rampart. Sandesha, Kandula and Savan do not appear on it.

So the cited source no longer supports the content it is cited for. Separately, the Apache Attic lists Apache Axis Sandesha2/C as "retired in September 2014" with "the move to the Attic … completed in July 2015" (https://attic.apache.org/projects/axis-sandesha-c.html), and also has entries for Savan/C and Savan/Java (dates on their respective Attic pages, which I have not checked).

I am not proposing deletion. An encyclopaedia should record that these modules existed, and removing them loses accurate history. What seems wrong is that they sit in a list that reads as a present-tense capability. Two options, and I have no preference between them:

• Keep the modules but mark the retired ones as historical, with the Attic citation

 and date for those the Attic covers; or

• Keep the current module list to what the cited source supports (Addressing and

 Rampart) and move the rest into a sentence about modules that are no longer
 maintained.

One caveat I should flag rather than leave for a reviewer to find: Kandula is not in the Attic, and Sandesha2's Java implementation is not either. For those two, absence from the current modules page is all I can source; I am not asking the article to call them retired.

6. The update banner

If items 1–5 are accepted the {{update}} banner may no longer be warranted, but that is a judgement for an uninvolved editor and I am not requesting its removal.

Deliberately not requested

One thing a reviewer might expect to see here, which I am leaving out on purpose:

• Model Context Protocol support in Axis2/C. It exists, but as a sample

 application rather than part of the framework core, and I do not think a sample
 belongs in a feature list. I would rather raise it later, if there is ever
 independent coverage to cite.

Happy to supply exact citation URLs for any item above, or to narrow anything a reviewer considers overstepping.

Iksrazal (talk) 13:37, 28 August 2026 (UTC)

Adding one item I missed when I posted the above; treating it as item 7.

The infobox |operating system= field reads "Cross-platform". For Axis2/C

that is thinner than what the project documents: it cross-compiles for Android. The

Axis2/C page states "Android Support - Cross-compile for ARM64/ARMv7 mobile devices"

(https://axis.apache.org/axis2/c/core/), and the same page describes

the project as a "HTTP/2 JSON-RPC web services framework for C with legacy SOAP

support", which is also a better citation for the JSON and HTTP/2 additions in item 3

than the release notes I pointed at there.

Proposed: name Android in the |operating system= field alongside

"Cross-platform", or add a clause to the deployment sentence in item 2. I would not

put it in the feature list, since that list is about protocols and message exchange

and Android is a platform rather than a feature — but a reviewer may disagree about

placement and I have no preference.

To be clear about scope, this is the only addition I want to make to the original

request. Iksrazal (talk) 20:50, 28 August 2026 (UTC)

Question: Did you use an AI to write this request? ^MetalBreaks_AndBends (One for all) 13:58, 1 September 2026 (UTC)

I did indeed use Claude Code to summarize my thoughts, under lots of my direction and review. I am a Wikipedia newbie and it wasn't obvious to me that AI could be a concern. Iksrazal (talk) 16:04, 1 September 2026 (UTC)

Ah, that's generally not advised. Using LLMs on talk pages can cause miscommunication, increase reading effort on the part of the (currently overloaded) reviewers, and can be seen by some as a... sign of disrespect. (its kinda weird, i know, but we get lots of ai generated edits that overload the mostly ai unassisted volunteers. there's more to it, but its real politicy) ^MetalBreaks_AndBends (One for all) 16:19, 1 September 2026 (UTC)

Thanks for the explanation, I'll be writing my own comments from here.

If it helps, I believe items 1 and 4 from my original post are clearly sourced. I am restating here for easier action while the rest can be dropped:

Item 1, the infobox stable release. The single figure listed as "2.0.0 (4 March 2025)" is out of date for Axis2/Java and does not include the latest release for Axis2/C. There is no one version that applies to both.

Suggested replacement:

Axis2/Java 2.0.1, 17 May 2026: https://central.sonatype.com/artifact/org.apache.axis2/axis2/2.0.1

Axis2/C 2.0.0, 27 April 2026: https://archive.apache.org/dist/axis/axis2/c/core/2.0.0/ (signed source release, signature and checksum all dated 27 April 2026)

Item 4, a stale URL. The source repository link points to the old Axis2/Java SVN location at https://svn.apache.org/repos/asf/axis/axis2/java/core/trunk/ instead of GitHub where new development takes place at https://github.com/apache/axis-axis2-java-core .

Item 1 proposes a release split, if that is accepted the matching repository for Axis2/C is https://github.com/apache/axis-axis2-c-core .

Iksrazal (talk) 20:34, 1 September 2026 (UTC)

I've made the repo and release date changes, although I only included axis2/java, as I didn't see a way to have multiple components covered by one infobox. As such, it may be a good idea to just add a second infobox. ^MetalBreaks_AndBends (One for all) 21:00, 1 September 2026 (UTC)