I have successfully deployed Axis 1.2 on Weblogic
8.1sp4 and can view the wsdl's for AdminService and
Version. The problem is when I use AdminClient to
deploy a webservice against a bean that was deployed
to WL in an ear file I get the following error on the
AxisServlet page:
AXIS error
Sorry, something seems to have gone wrong... here are
the details:
Fault - ; nested exception is:
java.lang.ClassNotFoundException:
foo.bar.webservice.ejb.CatalogWebService
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.ClassNotFoundException:
foo.bar.webservice.ejb.CatalogWebService
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:MY-PC
The deploy.wsdd file is:
<?xml version="1.0" encoding="UTF-8"?>
<deployment xmlns="http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";>
<service name="CatalogWebService"
provider="java:EJB">
<parameter name="beanJndiName"
value="CatalogWebServiceBean"/>
<parameter name="homeInterfaceName"
value="foo.bar.webservice.ejb.CatalogWebServiceLocalHome"/>
<parameter name="remoteInterfaceName"
value="foo.bar.webservice.ejb.CatalogWebService"/>
<parameter name="allowedMethods" value="*"/>
</service>
</deployment>
This configuration (ear and wsdd) work fine on JBoss,
but I need it to work on WebLogic as well. I have
added the Axis jar files (saaj, jaxrpc) to the front
of the CLASSPATH in the startup script. Also the JNDI
lookup on the bean can be successfully tested from the
weblogic console. Is there some problem with Axis
under weblogic not finding other jars/ears that are
deployed?
Any info would be greatly appreciated,
Mark
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
