axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mukesh" <muk...@hungama.com>
Subject RE: soapenc:string vs xsd:string
Date Thu, 29 Dec 2005 01:48:05 GMT
Hi,

 

 I must say thanks to iksrazal. I have used "-y  encoded" option with
Java2WSDL and problem solved it has yet to be tested at another end (person
who is using MSSoap ).

 

Anne: parameter name="dotNetSoapEncFix" value="true"/> is already added in
my /axis/WEB-INF/server-config.wsdd inside global tag. But I do know how it
will affect WSDL .

 

I have changed it to false and I did not see any effect. Do I Need to change
somewhere else too ?

 

-Mukesh

 

 

 

  _____  

From: Anne Thomas Manes [mailto:atmanes@gmail.com] 
Sent: Thursday, December 29, 2005 12:12 AM
To: axis-user@ws.apache.org
Subject: Re: soapenc:string vs xsd:string

 

I concur with iksrazel. Switch to wrapped document/literal.
But if for some reason that is not an option for you, then add this
parameter to your WSDD:
   <parameter name="dotNetSoapEncFix" value="true"/>

Anne

On 12/28/05, iksrazal <iksrazal@gmail.com> wrote:

Don't use soap encoding with .net - or really anywhere these days if you can
avoid it. Google for document/literal wrapped  - plenty of examples out
there.

HTH,
iksrazal
http://www.braziloutsource.com/

Em Quarta 28 Dezembro 2005 15:34, o mukesh escreveu:
> Hi friends,
>
>
>
>             I am using Axis1.3 + tomcat 5.5.12 on linux 7.0s.
>
>
>
>             I have developed a simple web service and deployed it. I can
> access it without problem from any tomcat + Axis server but I've got
> following error while trying to access from IIS + MSSoap Client running on

> WIN NT.
>
>
>
>
>
>
>
> WSDLReader:Analyzing the WSDL file failed HRESULT=0x80004005
> -WSDLReader:Initialization of service failed
>
> HRESULT=0x80004005 -WSDLService:Initialization of the port for service 
> HungamaMWSService failed
>
> HRESULT=0x80004005 - WSDLPort:Analyzing the binding information for port
> hungamamws failed HRESULT=0x80004005 - WSDLPort:An operation for port
> hungamamws could not be initialized HRESULT=0x80004005 - 
>
> WSDLOperation:Initializing of the input message failed for operation
> deliverMOMessage HRESULT=0x80004005 - WSDLOperation:Initialization of a
> SoapMapper for operation deliverMOMessage failed HRESULT=0x80004005 - 
>
> SoapMapper:The SoapMapper for element string could not be created
>
> HRESULT=0x80004005 - SoapMapper:The schema definition with a
> targetnamespace of http://schemas.xmlsoap.org/soap/encoding
>
>
>
> Well, problem was encoding (http://schemas.xmlsoap.org/soap/encoding )
> scheme as it is not understood by MSSoap. 
>
>             But I could not find any way to generate WSDL file without
> above scheme using Axis toolkit.
>
>
>
>             Excerpt from generated WSDL file
>
>
>
>  < http://202.87.41.147:2503/axis/services/hungamamws?wsdl##
<http://202.87.41.147:2503/axis/services/hungamamws?wsdl##> > -
> <wsdl:message name="deliverMOMessageRequest">
>
>   <wsdl:part name="in0" type="xsd:short" /> 
>
>   <wsdl:part name="in1" type="soapenc:string" />
>
>   <wsdl:part name="in2" type="soapenc:string" />
>
>   <wsdl:part name="in3" type="soapenc:string" /> 
>
>   <wsdl:part name="in4" type="soapenc:string" />
>
>   <wsdl:part name="in5" type="xsd:double" />
>
>   <wsdl:part name="in6" type="soapenc:string" /> 
>
>   <wsdl:part name="in7" type="soapenc:string" />
>
>   <wsdl:part name="in8" type="impl:ArrayOf_soapenc_string" />
>
>   <wsdl:part name="in9" type="xsd:int" /> 
>
>   </wsdl:message>
>
>
>
>        I need type="xsd:string" instead of  type="soapenc:string". Its
> little urgent.
>
>
>
>        Please suggest me how can I generate a WSDL which work on both kind

> of systems.
>
>
>
>  -Mukesh

--

 


Mime
View raw message