Background:
Axis provides a way to use pluggable providers - excerpt from org.apache.axis.deployment.wsdd.WSDDProvider (Axis source code) for method: private static void loadPluggableProviders()

/**
Look for file META-INF/services/org.apache.axis.deployment.wsdd.Provider
in all the JARS, get the classes listed in those files and add them to
providers list if they are valid providers.

Here is how the scheme would work.

A company providing a new provider will jar up their provider related
classes in a JAR file. The following file containing the name of the new
provider class is also made part of this JAR file.

META-INF/services/org.apache.axis.deployment.wsdd.Provider

By making this JAR part of the webapp, the new provider will be
automatically discovered.
*/

Adding the org.apache.axis.deployment.wsdd.Provider file to the META-INF directory in a WSR file use to work in jboss 3.2.2 however it does not seem to work in jboss 3.2.3.

I get the following exception when trying to access the services in any way while deployed in jboss 3.2.2:

17:12:11,096 INFO [EXCEPTIONS] Exception:
org.apache.axis.ConfigurationException: org.apache.axis.deployment.wsdd.WSDDException:
No provider type matches QName
'{http://xml.apache.org/axis/wsdd/providers/java}CustomRPC'
org.apache.axis.deployment.wsdd.WSDDException:
No provider type matches QName
'{http://xml.apache.org/axis/wsdd/providers/java}CustomRPC'
 at org.apache.axis.deployment.wsdd.WSDDProvider.getInstance(WSDDProvider.java:205)
 at org.apache.axis.deployment.wsdd.WSDDService.makeNewInstance(WSDDService.java:446)
 at org.jboss.net.axis.Deployment.getDeployedServices(Deployment.java:233)
 at org.apache.axis.configuration.FileProvider.getDeployedServices(FileProvider.java:321)
 at org.apache.axis.transport.http.AxisServlet.reportAvailableServices(AxisServlet.java:681)
 at org.apache.axis.transport.http.AxisServlet.doGet(AxisServlet.java:262)
.
.
.

Question:
Does anyone have any suggestions?