Yes .. it is possible to customize in the deployment descriptor 

<service name=...>
   <parameter name="wsdlServiceElement" value="..."/>
   <parameter name="wsdlServicePort" value="..."/>
   <parameter name="wsdlPortType" value="..."/>
</service>

-----Original Message-----
From: Kashif Noorani [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 01, 2004 12:17 PM
To: [EMAIL PROTECTED]
Subject: porttype name override?


Is it possible to specify the name of the portType to be used when axis
deploys a webservice using WSDD? I am running into a slight problem with my
web service since Axis generates wsdl and proxies that use the
implementation class name of my web service rather than the interface.

I have the following setup:

public interface TestService
{
...
}

public class TestServiceImpl implements TestService
{
...
}

---------------- start deploy.wsdd --------------------------- <deployment
xmlns="http://xml.apache.org/axis/wsdd/";
xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";
<service name="TestService" provider="java:RPC">
  <parameter name="className" value="TestServiceImpl"/>
  <parameter name="allowedMethods" value="*"/>
</service>
</deployment>

---------------- end deploy.wsdd ---------------------------

I am getting the following wsdl generated by Axis: <wsdl:portType
name="TestServiceImpl"> .... </wsdl:portType>

I am also getting the following proxy classes generated by Axis: public
interface TestServiceImpl extends java.rmi.Remote { .. }

public class TestServiceImplServiceLocator extends
org.apache.axis.client.Service implements
com.bmc.sms.webservice.client.TestServiceImplService
{
...
}


------------------------------------------------------------------------------
This message is intended only for the personal and confidential use of the
designated recipient(s) named above.  If you are not the intended recipient of
this message you are hereby notified that any review, dissemination,
distribution or copying of this message is strictly prohibited.  This
communication is for information purposes only and should not be regarded as
an offer to sell or as a solicitation of an offer to buy any financial
product, an official confirmation of any transaction, or as an official
statement of Lehman Brothers.  Email transmission cannot be guaranteed to be
secure or error-free.  Therefore, we do not represent that this information is
complete or accurate and it should not be relied upon as such.  All
information is subject to change without notice.

Reply via email to