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

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

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

Em Quarta 28 Dezembro 2005 15:34= , o mukesh escreveu:
> Hi friends,
>
>
>
>&nb= sp;            I am = using Axis1.3 + tomcat 5.5.12 on linux 7.0s.
>
>
>
>         &= nbsp;   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
> foll= owing error while trying to access from IIS + MSSoap Client running on
> WIN NT.
>
>
>
>
>
>
>> WSDLReader:Analyzing the WSDL file failed HRESULT=3D0x80004005
>= ; -WSDLReader:Initialization of service failed
>
> HRESULT=3D0x= 80004005 -WSDLService:Initialization of the port for service
> HungamaMWSService failed
>
> HRESULT=3D0x80004005 - WS= DLPort:Analyzing the binding information for port
> hungamamws failed= HRESULT=3D0x80004005 - WSDLPort:An operation for port
> hungamamws c= ould not be initialized HRESULT=3D0x80004005 -
>
> WSDLOperation:Initializing of the input message failed for= operation
> deliverMOMessage HRESULT=3D0x80004005 - WSDLOperation:In= itialization of a
> SoapMapper for operation deliverMOMessage failed = HRESULT=3D0x80004005 -
>
> SoapMapper:The SoapMapper for element string could not be = created
>
> HRESULT=3D0x80004005 - SoapMapper:The schema defini= tion 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 sc= heme using Axis toolkit.
>
>
>
>   &= nbsp;         Excerpt from generate= d WSDL file
>
>
>
>  < http://202.87.41.147:2503/axis/services/hungamamws?wsdl##> -
>= <wsdl:message name=3D"deliverMOMessageRequest">
>>   <wsdl:part name=3D"in0" type=3D"xsd:sho= rt" />
>
>   <wsdl:part name=3D"in1" type=3D&q= uot;soapenc:string" />
>
>   <wsdl:part na= me=3D"in2" type=3D"soapenc:string" />
>
>= ;   <wsdl:part name=3D"in3" type=3D"soapenc:str= ing" />
>
>   <wsdl:part name=3D"in4" type=3D&q= uot;soapenc:string" />
>
>   <wsdl:part na= me=3D"in5" type=3D"xsd:double" />
>
>&nb= sp; <wsdl:part name=3D"in6" type=3D"soapenc:string&= quot; />
>
>   <wsdl:part name=3D"in7" type=3D&q= uot;soapenc:string" />
>
>   <wsdl:part na= me=3D"in8" type=3D"impl:ArrayOf_soapenc_string" />>
>   <wsdl:part name=3D"in9" type=3D&quo= t;xsd:int" />
>
>   </wsdl:message>
>
>
><= br>>        I need type=3D"= xsd:string" instead of  type=3D"soapenc:string". I= ts
> little urgent.
>
>
>
>   =      Please suggest me how can I generate a WSDL w= hich work on both kind
> of systems.
>
>
>
>  -Mukesh
=
--