Hi,

I try to call an EJB from a client using axis web services. So I defined java:EJB as the Axis provider. All this work fine with JBoss 3.2.3. But I decided to switch to 3.2.6 and I have this kind of errors:

No provider type matches QName '{http://xml.apache.org/axis/wsdd/providers/java}EJB'

So I had a look at the definition of providers. This is what we have in 3.2.3:

static {
 providers.put(WSDDConstants.QNAME_JAVARPC_PROVIDER, new WSDDJavaRPCProvider());
 providers.put(WSDDConstants.QNAME_JAVAMSG_PROVIDER, new WSDDJavaMsgProvider());
 providers.put(WSDDConstants.QNAME_HANDLER_PROVIDER, new WSDDHandlerProvider());
 providers.put(WSDDConstants.QNAME_EJB_PROVIDER, new WSDDJavaEJBProvider());
 providers.put(WSDDConstants.QNAME_COM_PROVIDER, new WSDDComProvider());
 providers.put(WSDDConstants.QNAME_BSF_PROVIDER, new WSDDBsfProvider());
 providers.put(WSDDConstants.QNAME_CORBA_PROVIDER, new WSDDJavaCORBAProvider());
 providers.put(WSDDConstants.QNAME_RMI_PROVIDER, new WSDDJavaRMIProvider());
 try {
 loadPluggableProviders();
 } catch (Throwable t){
 String msg=t + JavaUtils.LS + JavaUtils.stackToString(t);
 log.info(Messages.getMessage("exception01",msg));
 }
 }

and this is what we have in 3.2.6:

static
 {
 providers.put(WSDDConstants.QNAME_JAVARPC_PROVIDER, new WSDDJavaRPCProvider());
 providers.put(WSDDConstants.QNAME_JAVAMSG_PROVIDER, new WSDDJavaMsgProvider());
 providers.put(WSDDConstants.QNAME_HANDLER_PROVIDER, new WSDDHandlerProvider());
 providers.put(WSDDConstants.QNAME_COM_PROVIDER, new WSDDComProvider());
 try
 {
 loadPluggableProviders();
 }
 catch (Throwable t)
 {
 String msg = t + JavaUtils.LS + JavaUtils.stackToString(t);
 log.info(Messages.getMessage("exception01", msg));
 }
 }

The EJBProvider is not loaded, and I think this is why I can't call EJB's from web services anymore. Is this a normal situation, or did I miss something ? Do we have to call EJB's differently now ?

Thanks for your help.

Maxime

PS: for testing purposes, I created a simple web service with 1 dummy method in a session EJB using JBuilder X with JBoss 3.2.x configuration, but I get the same behaviour.