hi
 
Thanks for the response. But i still have some problems. I have tried setting the namespace. Now the SOAP request is
 
<?xml version="1.0" encoding="UTF-8"?>
   <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <soapenv:Body> 
         <in0 xmlns="http://localhost:8080/Training/services/HelloWebService">World</in0>
      </soapenv:Body>
   </soapenv:Envelope>
 
I get the message No such operation 'in0'.
 
Unlike where the in0 is wrapped in another element. "document" does not have this wrapper. So the ? still persists.
 
Do u have any exmaple code for style "document"?
 
Regards
Krishnakumar B
-----Original Message-----
From: Oliver Adler [mailto:[EMAIL PROTECTED]
Sent: Friday, March 07, 2003 12:54 PM
To: [EMAIL PROTECTED]
Subject: AW: Using style Document in WSDD For Deployment

hi
 
the problem ist the empty namespace in in0 element.
Axis generates in the client ..Stub a wrong namespace definition.
When you open the stub you will find the following declaration:

static org.apache.axis.description.OperationDesc [] _operations;

static {

_operations = new org.apache.axis.description.OperationDesc[1];

org.apache.axis.description.OperationDesc oper;

oper = new org.apache.axis.description.OperationDesc();

oper.setName("MyOperationName");

oper.addParameter(new javax.xml.namespace.QName("", "data"), new javax.xml.namespace.QName("MYNamespace", "data"), de.geno.www.services.genotypes.Genodaten.class, org.apache.axis.description.ParameterDesc.IN, false, false);

 

Change the "" to your namespace and axis should find your service. The namespace should be the same as the namespace you have defined in your server-config.wsdd

 

Regards

 

Oliver

-----Ursprüngliche Nachricht-----
Von: Krishnakumar B [mailto:[EMAIL PROTECTED]
Gesendet: Fr 07.03.2003 4.35 Uhr
An: [EMAIL PROTECTED]
Cc:
Betreff: RE: Using style Document in WSDD For Deployment

hi
 
the tcpmon request is as follows
 
POST /Training/services/HelloWebService HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.0
Host: localhost
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: ""
Content-Length: 295
 
<?xml version="1.0" encoding="UTF-8"?>
   <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <soapenv:Body> 
         <in0 xmlns="">World</in0>
      </soapenv:Body>
   </soapenv:Envelope>
 
Regards
Krishnakumar B
-----Original Message-----
From: Oliver Adler [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2003 6:23 PM
To: [EMAIL PROTECTED]
Subject: AW: Using style Document in WSDD For Deployment

please use the tcpmon to look what is on the wire and publish it - the wsdd look fine to me
-----Ursprüngliche Nachricht-----
Von: Krishnakumar B [mailto:[EMAIL PROTECTED]
Gesendet: Do 06.03.2003 13.29 Uhr
An: [EMAIL PROTECTED]
Cc:
Betreff: RE: Using style Document in WSDD For Deployment

hi
 
I have tried adding ot the server-config.wsdd. It does not work. I have added the file below. Is this right?
 
Regards
Krishnakumar B
 
<?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">
 <globalConfiguration>
  <parameter name="adminPassword" value="admin"/>
  <parameter name="attachments.Directory" value="C:\Tomcat 4.1\webapps\Training\WEB-INF\attachments"/>
  <parameter name="sendMultiRefs" value="true"/>
  <parameter name="sendXsiTypes" value="true"/>
  <parameter name="attachments.implementation" value="org.apache.axis.attachments.AttachmentsImpl"/>
  <parameter name="sendXMLDeclaration" value="true"/>
  <requestFlow>
   <handler type="java:org.apache.axis.handlers.JWSHandler">
    <parameter name="scope" value="session"/>
   </handler>
   <handler type="java:org.apache.axis.handlers.JWSHandler">
    <parameter name="scope" value="request"/>
    <parameter name="extension" value=".jwr"/>
   </handler>
  </requestFlow>
 </globalConfiguration>
 <handler name="RPCDispatcher" type="java:org.apache.axis.providers.java.RPCProvider"/>
 <handler name="MsgDispatcher" type="java:org.apache.axis.providers.java.MsgProvider"/>
 <handler name="LocalResponder" type="java:org.apache.axis.transport.local.LocalResponder"/>
 <handler name="Authenticate" type="java:org.apache.axis.handlers.SimpleAuthenticationHandler"/>
 <handler name="URLMapper" type="java:org.apache.axis.handlers.http.URLMapper"/>
 <service name="Version" provider="java:RPC">
  <parameter name="allowedMethods" value="getVersion"/>
  <parameter name="className" value="org.apache.axis.Version"/>
 </service>
 <service name="AdminService" provider="java:MSG">
  <parameter name="allowedMethods" value="AdminService"/>
  <parameter name="enableRemoteAdmin" value="false"/>
  <parameter name="className" value="org.apache.axis.utils.Admin"/>
  <namespace>http://xml.apache.org/axis/wsdd/</namespace>
 </service>
 <service name="HelloWebService" provider="java:RPC" >
  <namespace>http://localhost:8080/Training/services/HelloWebService</namespace>
  <parameter name="allowedMethods" value="*"/>
  <parameter name="scope" value="Application"/>
  <parameter name="className" value="HelloWebService"/>
 </service>
 <transport name="local">
  <responseFlow>
   <handler type="java:org.apache.axis.transport.local.LocalResponder"/>
  </responseFlow>
 </transport>
 <transport name="http">
  <requestFlow>
   <handler type="URLMapper"/>
   <handler type="java:org.apache.axis.handlers.http.HTTPAuthHandler"/>
  </requestFlow>
 </transport>
</deployment>
-----Original Message-----
From: Oliver Adler [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2003 4:56 PM
To: [EMAIL PROTECTED]
Subject: AW: Using style Document in WSDD For Deployment

Hi,
 
try to add the following to your service description in your server-config.wsdd
<namespace>[namespace of the first body child]</namespace>
 
this enables axis to dispatch to the correct service.
 
Regards
Oliver
 

____________________________________________________________________

Oliver Adler, Senior Consultant
SYRACOM Systems AG - "The IT-Architects"

Otto-von-Guericke-Ring 15
D-65205 Wiesbaden

Tel +49 6122-9176-0
Fax +49 6122-9176-11
Mobil +49 175-1853998

E-Mail: [EMAIL PROTECTED]
<www.SYRACOM.de>

Ein Unternehmen der SYRACOM Gruppe - "The Business- & IT-Architects"

____________________________________________________________________

-----Ursprüngliche Nachricht-----
Von: Krishnakumar B [mailto:[EMAIL PROTECTED]
Gesendet: Do 06.03.2003 12.10 Uhr
An: [EMAIL PROTECTED]
Cc:
Betreff: Using style Document in WSDD For Deployment

Hi
 
I am deploying a web service with in the WSDD file. When i invoke this webservice from a client it says
No such operation in0. I got the SOAP message using TCPMonitor. The same web service works when i say .
 
How do i make the work?
 
Would be glad for any help.
 
The SOAP message is
 
<?xml version="1.0" encoding="UTF-8"?>
   <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <soapenv:Body> 
         <in0 xmlns="">World</in0>
      </soapenv:Body>
   </soapenv:Envelope>
 
The WSDL for web service given by AXIS is
 
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://localhost:8080/Training/services/HelloWebService" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://localhost:8080/Training/services/HelloWebService" xmlns:intf="http://localhost:8080/Training/services/HelloWebService" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">>
 
   
 
 
   
 
 
   
     
     
   
 
 
    http://localhost:8080/Training/services/HelloWebService"/>
    </wsdl:port>
  </wsdl:service>
</wsdl:definitions>
 
Regards
Krishnakumar B

DISCLAIMER:
This message (including attachment if any) is confidential and may be privileged. Before opening attachments please check them for viruses and defects. MindTree Consulting Private Limited (MindTree) will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside. If you have received this message by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change and MindTree shall not be liable for any improper, untimely or incomplete transmission

DISCLAIMER:
This message (including attachment if any) is confidential and may be privileged. Before opening attachments please check them for viruses and defects. MindTree Consulting Private Limited (MindTree) will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside. If you have received this message by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change and MindTree shall not be liable for any improper, untimely or incomplete transmission.

DISCLAIMER:
This message (including attachment if any) is confidential and may be privileged. Before opening attachments please check them for viruses and defects. MindTree Consulting Private Limited (MindTree) will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside. If you have received this message by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change and MindTree shall not be liable for any improper, untimely or incomplete transmission.

Reply via email to