Fork of Apache XML-RPC

Apache XML-RPC is no longer officially maintained by Apache. This is a simple fork for the purposes of:

1. Applying the latest security patches.
2. Providing support for Jakarta EE 5+, i.e.: jakarta.javax

• The Apache XML-RPC source code was imported to Git from the archived SVN Apache XML-RPC repository at: https://svn.apache.org/repos/asf/webservices/archive/xmlrpc/
• The security patches were obtained from the Fedora project's package at: https://download-ib01.fedoraproject.org/pub/fedora/linux/releases/34/Everything/source/tree/Packages/x/xmlrpc-3.1.3-28.fc34.src.rpm
  • Whilst 6 patches are available, the 2nd patch for OSGI metadata has not been applied as PR: XMLRPC-184 (see commit: f0b8977) exists in the main line of this code base and already adds some conflicting OSGI metadata support.

NOTE: This fork was created for our own purposes, and we offer no guarantee that we will maintain it beyond our own requirements.

NOTE: The version 4.x.x line contains only the original source code plus the security updates, whereas the 5.x.x line also contains changes to switch from the javax.servlet package namespace to Jakarta EE's jakarta.servlet package namespace.

However, if you want a possibly more secure Apache XML-RPC than the last official version (3.1.3), then this fork's artifacts are available from Maven Central as:

XML-RPC Server

    <dependency>    
        <groupId>com.evolvedbinary.thirdparty.org.apache.xmlrpc</groupId>
        <artifactId>xmlrpc-server</artifactId>
        <version>5.0.0</version>
    </dependency>

XML-RPC Client

    <dependency>    
        <groupId>com.evolvedbinary.thirdparty.org.apache.xmlrpc</groupId>
        <artifactId>xmlrpc-client</artifactId>
        <version>5.0.0</version>
    </dependency>

XML-RPC Common

    <dependency>    
        <groupId>com.evolvedbinary.thirdparty.org.apache.xmlrpc</groupId>
        <artifactId>xmlrpc-common</artifactId>
        <version>5.0.0</version>
    </dependency>

Perfoming a Release

To release a new version for Evolved Binary to Maven Central, simply run:

mvn -Dmaven.site.skip=true -Dmaven.site.deploy.skip=true -Dgpg.keyname=D4A08A8AB731BF576354A8183EF2B4866A540119 -Darguments="-Dmaven.site.skip=true -Dmaven.site.deploy.skip=true -Dgpg.keyname=D4A08A8AB731BF576354A8183EF2B4866A540119" release:prepare

...

mvn -Dmaven.site.skip=true -Dmaven.site.deploy.skip=true -Dgpg.keyname=D4A08A8AB731BF576354A8183EF2B4866A540119 -Darguments="-Dmaven.site.skip=true -Dmaven.site.deploy.skip=true -Dgpg.keyname=D4A08A8AB731BF576354A8183EF2B4866A540119" release:perform

Then visit https://oss.sontatype.org and login, and release the staged artifacts to Maven Central