I am facing similar issue with addressing.mar while consuming a service using Axis2.

In my case the axis2 file was in a jar added as a dependency in ear / lib.

The workaround that worked for me was to place this mar file outside ear / war and then provide the repo url while initializing the ConfigurationContextFactory.

I placed the mar file under {jboss.server.config.dir}/modules. Also, added the modules.list file (which contains just the name of the mar file / files).

Example

ConfigurationContextFactory .createConfigurationContextFromURIs(<path to axis2ConfigFileURL>, file:///${jboss.server.config.dir} );

In case, the axis2.xml file is available directly inside WEB-INF, we can use the following code and create the modules directory under WEB-INF. Don't forget to add the modules.list file (as mentioned below).

File axis2RepositorURLFile = new File("vfs:///deployment/<ear or war> / WEB-INF");  (or try vfs:///content/ <ear or war> / WEB-INF

ConfigurationContextFactory.createConfigurationContextFromURIs(null,  axis2RepositorURLFile.toURI().toURL());

But its still a work around. Please let know, in case you were to resolve it in a clean way.