At 18:34 11/11/2002 +0530, you wrote:
I'm not sure, but would hazard a guess that the this is due to the version of jboss.net that you have.Hi Guys, I have deployed a webservice onto JBoss-3.0.2. The web-service.xml file looks like this ,<deployment xmlns="http://xml.apache.org/axis/wsdd/"; xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"; targetNamespace="http://net.jboss.org/nEngineApplicationServer"; xmlns:nEngineApplicationServer="http://net.jboss.org/nEngineApplicationServe r" xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";> <!-- this is an extension to the Axis deployment descriptor which allows to specify the naming environment for the deployed ws logic --> <ejb-ref> <ejb-ref-name>nEngineApplicationServer</ejb-ref-name> <ejb-link>nEngineApplicationServer</ejb-link> </ejb-ref> <service name="nEngineService" provider="Handler"> <parameter name="handlerClass" value="org.jboss.net.axis.server.EJBProvider"/> <parameter name="beanJndiName" value="java:comp/env/nEngineApplicationServer.ApplicationServerHome"/> <parameter name="homeInterfaceName" value="ApplicationServerHome"/> <parameter name="allowedMethods" value="*"/> <requestFlow name="nEngineServiceRequest"> <handler name "TransactionRequestHandler" type="java:org.jboss.net.axis.server.TransactionRequestHandler"/> </requestFlow> <responseFlow name="nEngineServiceResponse"> <handler name="SerialisationResponseHandler" type="java:org.jboss.net.axis.server.SerialisationResponseHandler"/> <handler name="TransactionResponseHandler" type="java:org.jboss.net.axis.server.TransactionResponseHandler"/> </responseFlow> </service> </deployment> I am unable to view the wsdl of the service when i do the following, http://localhost:8080/axis/services/nEngineService?wsdl It says that one particular entity bean has not been bound. But when i see the jmx-console that bean is listed in the JNDIVIEW Further more in the following link http://localhost:8080/axis/services?list i can distictly see my Service listed. You can also reach me at [EMAIL PROTECTED] Any ideas on this problem , Thanks in advance Dhiraj Ramakrishan
I found that some of the earlier one's would give me a wsdl for some apps, but not others. For example, I could get one for a simple wsr one, ie a service not included in a larger app, but could not get one for accessing an ejb. Maybe this is the same problem that you have.
Try your service in a jboss-3.2 version and see if it's ok in that. Note, that this uses a different version of axis, so your code may need a bit of tweaking.
cheers,
Bruce
Dr. Bruce Scharlau
Dept. of Computing Science
University of Aberdeen
Aberdeen AB24 3UE
01224 272193
http://www.csd.abdn.ac.uk/~bscharla
mailto:scharlau@;csd.abdn.ac.uk
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
