axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Champailler <schampail...@easynet.be>
Subject No provider type matches QName
Date Tue, 28 Sep 2004 10:13:13 GMT
Dear you all,

I continue to try to integrate  Axis 1.2beta in JBoss 4.0.0.

I had some troubles, but they are fixed (check 
http://marc.theaimsgroup.com/?l=axis-user&m=109635859926921&w=2).

Now, I've got something else.

I tried to tie a web serice to an EJB. I followed the sample given in the Axis 
disitribution (in samples/ejb). With JBoss 3.2.5 everything work as expected 
so far (I can see the service and it generates its WSDL fine). I deploy my 
webservice as a war file containing all the libs axis needs as well as its 
"original" web.xml (hte one that is given in the webapps directory of the 
distribution).

However, in JBoss 4.0.0, Axis complains like this when I try to reach 
http://localhost:8080/foundry/servlet/AxisServlet (after having deployed the 
WSDD file of my service, without apparent trouble) :

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

It looks like Axis can't find the EJB provider, and I have not much clue where 
to start to look... Another thing to note is that if I /don't/ deploy my WSDD 
file, then the http://localhost.../AxisServlet page just displays fine... It 
starts to fail as soon as I deploy the WSDD.

If you wonder, my WSDD is like this :

<?xml version="1.0"?>
<deployment xmlns="http://xml.apache.org/axis/wsdd/"
            xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">

<service name="SimpleBean" provider="java:EJB">
    <parameter name="beanJndiName" value="local/ProjectService"/>
    <parameter name="homeInterfaceName" 
value="foundryserver.beans.interfaces.ProjectServiceHome"/>
    <parameter name="remoteInterfaceName" 
value="foundryserver.beans.interfaces.ProjectService"/>
    <parameter name="allowedMethods" value="getProject"/>
</service>

</deployment>


Maybe the namespace declaration is confusing ?

Thank you for your patience.

Stefan

Mime
View raw message