RE: is it possible to change soapenc:string to xsd:string in generated WSDL?

[Merten Schumann]

Title: RE: is it possible to change soapenc:string to xsd:string in generated WSDL?

YES, this "dotNetSoapEncFix" works and solves my problem! I forgot to restart my Axis web app with my first try.

 

Thank you very much aedemar for the tip and Axis team for the fix! :-)

 

cu

   Merten

---

From: Merten Schumann [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 15, 2005 6:03 PM
To: axis-user@ws.apache.org
Subject: RE: is it possible to change soapenc:string to xsd:string in generated WSDL?

Wow, aedemar, thank you, that looks exactly like what I need. Tried it with 1.2RC3, but seems to have no effect, there are still these soapenc:string beasts in the generated WSDL ... Will continue my tries ...

 

cu

   Merten

---

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 15, 2005 5:51 PM
To: axis-user@ws.apache.org
Subject: RE: is it possible to change soapenc:string to xsd:string in generated WSDL?

see http://issues.apache.org/jira/browse/AXIS-1834.

They say it can be solved with by adding the new "dotNetSoapEncFix" flag in your server-config.wsdd's globalConfiguration section. Axis documentation has more info.

-----Original Message-----
From: Merten Schumann [mailto:[EMAIL PROTECTED]]
Sent: 15 March 2005 4:46
To: axis-user@ws.apache.org
Subject: is it possible to change soapenc:string to xsd:string in
generated WSDL?

Hello,

when testing my web service (Axis 1.2RC3) with MS SOAPToolkit 3.0 I
found that it's not working obviously due to this soapenc:string
encodings instead of xsd:string. I found some cries for help regarding
this interop issue in the web, but no solution as far as I could see.
Maybe you've seen this message from MSSoapInit too "SoapMapper for
element string could not be created".

I could try to hand over my own WSDL file (created with Sun's wscompile
from J2EE stuff) to the WSDD deploy step, but I guess Axis will not
accept it or so.

My Perl and Python clients work fine. Some .NET stuff too. But I need
this MS SOAPToolkit stuff (to use the Axis powered web service from VBA
in MS Office documents). I think it's a problem in the SOAPToolkit, not
in Axis, but the SOAPToolkit is there and will not be changed/supported
in the future ...

For boolean, Axis is using xsd:boolean. Is there a way to let Axis
create xsd:string elements?

Thanx a lot!
   Merten

------------------------------------------------------------
This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately.

Ce courrier électronique est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courrier électronique par erreur, veuillez m'en aviser immédiatement, par retour de courrier électronique ou par un autre moyen.

============================================================