Hey Keith, 

I fixed it. It was my services,xml - defining actionMapping as >/"/"< , I 
changed it to >""< and it worked. Thanks a lot for your help. 

Regards, 

Srikanth Muthyala 



----- Original Message ----- 
From: "Srikanth Muthyala" <[EMAIL PROTECTED]> 
To: axis-user@ws.apache.org 
Cc: [EMAIL PROTECTED] 
Sent: Monday, 15 October 2007 09:54:36 PM (GMT+1000) Australia/Sydney 
Subject: Re: Axis 2 client part of web app 





Hi keith, 

I have tried stub._serviceClient.getOptions().setAction(""); but didnt help. 
Here is the wsdl..... 

  <? xml version="1.0" encoding="UTF-8" ?> 

- < definitions name =" rtbCallEvent " targetNamespace =" urn:rtbCallEvent/wsdl 
" xmlns:tns =" urn:rtbCallEvent/wsdl " xmlns:xsd =" 
http://www.w3.org/2001/XMLSchema " xmlns:ns2 =" urn:rtbCallEvent/types " 
xmlns:soap =" http://schemas.xmlsoap.org/wsdl/soap/ " xmlns =" 
http://schemas.xmlsoap.org/wsdl/ " > 


- < types > 


- < schema targetNamespace =" urn:rtbCallEvent/types " xmlns =" 
http://www.w3.org/2001/XMLSchema " xmlns:soap11-enc =" 
http://schemas.xmlsoap.org/soap/encoding/ " xmlns:tnsT =" 
urn:rtbCallEvent/types " xmlns:wsdl =" http://schemas.xmlsoap.org/wsdl/ " 
xmlns:xsi =" http://www.w3.org/2001/XMLSchema-instance " > 


- < complexType name =" callEvent " > 


- < sequence > 


  < element name =" recordId " nillable =" false " type =" string " /> 

  < element name =" direction " nillable =" false " type =" string " /> 

  < element name =" callingNumber " nillable =" false " type =" string " /> 

  < element name =" calledNumber " nillable =" false " type =" string " /> 

  < element name =" answerTime " nillable =" false " type =" string " /> 

  < element name =" releaseTime " nillable =" false " type =" string " /> 

  < element name =" group " nillable =" false " type =" string " /> 
  </ sequence > 
  </ complexType > 

- < complexType name =" callEventResponse " > 


- < sequence > 


  < element name =" result " type =" boolean " /> 
  </ sequence > 
  </ complexType > 

  < element name =" callEvent " type =" tnsT:callEvent " /> 

  < element name =" callEventResponse " type =" tnsT:callEventResponse " /> 
  </ schema > 
  </ types > 

- < message name =" rtbCallEventSEI_callEvent " > 


  < part name =" parameters " element =" ns2:callEvent " /> 
  </ message > 

- < message name =" rtbCallEventSEI_callEventResponse " > 


  < part name =" result " element =" ns2:callEventResponse " /> 
  </ message > 

- < portType name =" rtbCallEventSEI " > 


- < operation name =" callEvent " > 


  < input message =" tns:rtbCallEventSEI_callEvent " /> 

  < output message =" tns:rtbCallEventSEI_callEventResponse " /> 
  </ operation > 
  </ portType > 

- < binding name =" rtbCallEventSEIBinding " type =" tns:rtbCallEventSEI " > 


  < soap:binding style =" document " transport =" 
http://schemas.xmlsoap.org/soap/http " /> 

- < operation name =" callEvent " > 


  < soap:operation soapAction =" " /> 

- < input > 


  < soap:body use =" literal " /> 
  </ input > 

- < output > 


  < soap:body use =" literal " /> 
  </ output > 
  </ operation > 
  </ binding > 

- < service name =" RtbCallEvent " > 


- < port name =" rtbCallEventSEIPort " binding =" tns:rtbCallEventSEIBinding " 
> 


  < soap:address location =" 
http://10.0.0.66:8888/RTBCustomer/services/RtbCallEvent " /> 
  </ port > 
  </ service > 
  </ definitions > 

Regards, 

Srikanth Muthyala 

Snr Consultant 
Innovative IT Consultants 

Mobile: +61 401 544 199 
Email:[EMAIL PROTECTED] 

www.iitc.com.au 

----- Original Message ----- 
From: "keith chapman" <[EMAIL PROTECTED]> 
To: axis-user@ws.apache.org 
Sent: Monday, 15 October 2007 06:22:05 PM (GMT+1000) Australia/Sydney 
Subject: Re: Axis 2 client part of web app 

Hi Srikanth, 

When your using the webapp is looks like addressing is engaged. As a workaround 
just set this option on the client 

stub._serviceClient.getOptions().setAction(""); 

As a better solluion can you send me the interface operation section of your 
?wsdl2. Or the whole wsdl. Looks like there is a mismatch in the addreassing 
header in the client and the server. 

Thanks, 
Keith. 

Reply via email to