Return-Path: 
 <axis-user-return-39588-apmail-ws-axis-user-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-user-archive@www.apache.org
Received: (qmail 33113 invoked from network); 29 Dec 2005 01:51:48 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 29 Dec 2005 01:51:48 -0000
Received: (qmail 37781 invoked by uid 500); 29 Dec 2005 01:51:37 -0000
Delivered-To: apmail-ws-axis-user-archive@ws.apache.org
Received: (qmail 37763 invoked by uid 500); 29 Dec 2005 01:51:37 -0000
Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-user@ws.apache.org
list-help: <mailto:axis-user-help@ws.apache.org>
list-unsubscribe: <mailto:axis-user-unsubscribe@ws.apache.org>
List-Post: <mailto:axis-user@ws.apache.org>
List-Id: <axis-user.ws.apache.org>
Delivered-To: mailing list axis-user@ws.apache.org
Received: (qmail 37752 invoked by uid 99); 29 Dec 2005 01:51:37 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Dec 2005 17:51:37 -0800
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=HTML_MESSAGE
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Received: from [202.87.39.91] (HELO smtp1.netmagicians.com) (202.87.39.91)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Dec 2005 17:51:35 -0800
Received: from netbox.hungama.com (unknown [202.87.45.8])
	by smtp1.netmagicians.com (Postfix) with ESMTP id 87D978EC376
	for <axis-user@ws.apache.org>; Thu, 29 Dec 2005 07:21:06 +0530 (IST)
Received: from mukesh (unknown [10.0.0.227])
	by netbox.hungama.com (Postfix) with ESMTP id 2BC14DC3E7
	for <axis-user@ws.apache.org>; Thu, 29 Dec 2005 07:26:35 +0530 (IST)
From: "mukesh" <mukesh@hungama.com>
To: <axis-user@ws.apache.org>
Subject: RE: soapenc:string vs xsd:string
Date: Thu, 29 Dec 2005 07:18:05 +0530
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0019_01C60C48.036495A0"
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcYMGHzZjhx5XokmSkqgsuhhYkB9VwAAF9mA
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <bf414ee60512281041j51c2027eo589117e6cc5b1daa@mail.gmail.com>
Message-Id: <20051229015635.2BC14DC3E7@netbox.hungama.com>
X-NetMagic-MailScanner: Found to be clean, Found to be clean
X-NetMagic-MailScanner-SpamCheck: 
X-NetMagic-MailScanner-Information: Powered By NetMagic Mail Protection v1.0
X-NetMagic-MailScanner-From: mukesh@hungama.com
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

This is a multi-part message in MIME format.

------=_NextPart_000_0019_01C60C48.036495A0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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

--

 


------=_NextPart_000_0019_01C60C48.036495A0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:blue;
	text-decoration:underline;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:Arial;
	color:navy;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dblue>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Hi,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>&nbsp;I must say thanks to =
iksrazal. I have
used &#8220;&#8211;y &nbsp;encoded&#8221; option with Java2WSDL and =
problem solved
it has yet to be tested at another end (person who is using MSSoap =
).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Anne: <b><span =
style=3D'font-weight:bold'>parameter
name=3D&quot;dotNetSoapEncFix&quot; =
value=3D&quot;true&quot;/&gt;</span></b> is
already added in my /axis/WEB-INF/server-config.wsdd inside global tag. =
But I do
know how it will affect WSDL .<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I have changed it to false and I =
did not see
any effect. Do I Need to change somewhere else too =
?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>-Mukesh<o:p></o:p></span></font></p>=


<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font =
size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>

<hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1>

</span></font></div>

<p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font =
size=3D2
face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Anne =
Thomas
Manes [mailto:atmanes@gmail.com] <br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, December =
29, 2005
12:12 AM<br>
<b><span style=3D'font-weight:bold'>To:</span></b> =
axis-user@ws.apache.org<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> Re: =
soapenc:string vs
xsd:string</span></font><o:p></o:p></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D3
face=3D"Times New Roman"><span style=3D'font-size:12.0pt'>I concur with =
iksrazel.
Switch to wrapped document/literal.<br>
But if for some reason that is not an option for you, then add this =
parameter
to your WSDD:<br>
&nbsp;&nbsp; &lt;parameter name=3D&quot;dotNetSoapEncFix&quot;
value=3D&quot;true&quot;/&gt;<br>
<br>
Anne<o:p></o:p></span></font></p>

<div>

<p class=3DMsoNormal><span class=3Dgmailquote><font size=3D3 =
face=3D"Times New Roman"><span
style=3D'font-size:12.0pt'>On 12/28/05, <b><span =
style=3D'font-weight:bold'>iksrazal</span></b>
&lt;<a href=3D"mailto:iksrazal@gmail.com">iksrazal@gmail.com</a>&gt; =
wrote:</span></font></span><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>Don't use soap encoding with .net - or really anywhere these =
days if
you can<br>
avoid it. Google for document/literal wrapped&nbsp;&nbsp;- plenty of =
examples
out<br>
there.<br>
<br>
HTH,<br>
iksrazal<br>
<a =
href=3D"http://www.braziloutsource.com/">http://www.braziloutsource.com/<=
/a><br>
<br>
Em Quarta 28 Dezembro 2005 15:34, o mukesh escreveu:<br>
&gt; Hi friends,<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; I
am using Axis1.3 + tomcat 5.5.12 on linux 7.0s.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; I
have developed a simple web service and deployed it. I can<br>
&gt; access it without problem from any tomcat + Axis server but I've =
got<br>
&gt; following error while trying to access from IIS + MSSoap Client =
running on
<br>
&gt; WIN NT.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; WSDLReader:Analyzing the WSDL file failed HRESULT=3D0x80004005<br>
&gt; -WSDLReader:Initialization of service failed<br>
&gt;<br>
&gt; HRESULT=3D0x80004005 -WSDLService:Initialization of the port for =
service <br>
&gt; HungamaMWSService failed<br>
&gt;<br>
&gt; HRESULT=3D0x80004005 - WSDLPort:Analyzing the binding information =
for port<br>
&gt; hungamamws failed HRESULT=3D0x80004005 - WSDLPort:An operation for =
port<br>
&gt; hungamamws could not be initialized HRESULT=3D0x80004005 - <br>
&gt;<br>
&gt; WSDLOperation:Initializing of the input message failed for =
operation<br>
&gt; deliverMOMessage HRESULT=3D0x80004005 - =
WSDLOperation:Initialization of a<br>
&gt; SoapMapper for operation deliverMOMessage failed =
HRESULT=3D0x80004005 - <br>
&gt;<br>
&gt; SoapMapper:The SoapMapper for element string could not be =
created<br>
&gt;<br>
&gt; HRESULT=3D0x80004005 - SoapMapper:The schema definition with a<br>
&gt; targetnamespace of <a =
href=3D"http://schemas.xmlsoap.org/soap/encoding">http://schemas.xmlsoap.=
org/soap/encoding</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Well, problem was encoding (<a
href=3D"http://schemas.xmlsoap.org/soap/encoding">http://schemas.xmlsoap.=
org/soap/encoding</a>
)<br>
&gt; scheme as it is not understood by MSSoap. <br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
But I could not find any way to generate WSDL file without<br>
&gt; above scheme using Axis toolkit.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;
Excerpt from generated WSDL file<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp;&lt;<a
href=3D"http://202.87.41.147:2503/axis/services/hungamamws?wsdl##"> =
http://202.87.41.147:2503/axis/services/hungamamws?wsdl##</a>&gt;
-<br>
&gt; &lt;wsdl:message name=3D&quot;deliverMOMessageRequest&quot;&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp; &lt;wsdl:part name=3D&quot;in0&quot; =
type=3D&quot;xsd:short&quot;
/&gt; <br>
&gt;<br>
&gt;&nbsp;&nbsp; &lt;wsdl:part name=3D&quot;in1&quot;
type=3D&quot;soapenc:string&quot; /&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp; &lt;wsdl:part name=3D&quot;in2&quot;
type=3D&quot;soapenc:string&quot; /&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp; &lt;wsdl:part name=3D&quot;in3&quot;
type=3D&quot;soapenc:string&quot; /&gt; <br>
&gt;<br>
&gt;&nbsp;&nbsp; &lt;wsdl:part name=3D&quot;in4&quot;
type=3D&quot;soapenc:string&quot; /&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp; &lt;wsdl:part name=3D&quot;in5&quot; =
type=3D&quot;xsd:double&quot;
/&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp; &lt;wsdl:part name=3D&quot;in6&quot;
type=3D&quot;soapenc:string&quot; /&gt; <br>
&gt;<br>
&gt;&nbsp;&nbsp; &lt;wsdl:part name=3D&quot;in7&quot; =
type=3D&quot;soapenc:string&quot;
/&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp; &lt;wsdl:part name=3D&quot;in8&quot;
type=3D&quot;impl:ArrayOf_soapenc_string&quot; /&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp; &lt;wsdl:part name=3D&quot;in9&quot; =
type=3D&quot;xsd:int&quot;
/&gt; <br>
&gt;<br>
&gt;&nbsp;&nbsp; &lt;/wsdl:message&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;I need
type=3D&quot;xsd:string&quot; instead
of&nbsp;&nbsp;type=3D&quot;soapenc:string&quot;. Its<br>
&gt; little urgent.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Please suggest me =
how can I
generate a WSDL which work on both kind <br>
&gt; of systems.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&nbsp;&nbsp;-Mukesh<br>
<br>
--<o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------=_NextPart_000_0019_01C60C48.036495A0--