ok, will do this tomorrow (issues.apache.org is not responding to me when I try 
to step to Axis project right now, maybe a lot of load or so) ... and I will 
try to add a feature request, not open a bug :-)

   Merten

> -----Original Message-----
> From: Davanum Srinivas [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, March 15, 2005 6:29 PM
> To: [email protected]
> Subject: Re: is it possible to change soapenc:string to 
> xsd:string in generated WSDL?
> 
> Please open a bug report asking for an enhancement
> 
> thanks,
> dims
> 
> 
> On Tue, 15 Mar 2005 18:20:33 +0100, Merten Schumann
> <[EMAIL PROTECTED]> wrote:
> >  
> > My first fault was to put it in my service' wsdd file. But 
> it seems it's
> > only in the global configuration supported ... Maybe that's 
> why it's not
> > working for you (or you simply need to restart/redeploy 
> your service, to let
> > Axis generate the WSDL again ...) 
> >   
> > And here's my question to the Axis team (but maybe I should 
> post it with a
> > more specific subject): could this "dotNetSoapEncFix" be 
> supported in the
> > per-service deployment stuff too??? That would make it more 
> handy. I mean, I
> > could give people way easyli a deploy.wsdd for my service 
> with this fix
> > switch set to true. But it's not so simple to say "please 
> put this and that
> > to the global configuration settings in your 
> server-config.wsdd file". And
> > it would allow to apply this fix per service, not globally 
> for all ... 
> >   
> > cu 
> >    Merten
> >  
> >  
> >  ________________________________
> >  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> > Sent: Tuesday, March 15, 2005 6:07 PM
> > To: [email protected]
> > Subject: RE: is it possible to change soapenc:string to 
> xsd:string in
> > generated WSDL?
> > 
> >  
> >  
> > I couldn't get it to work either - that's why I said "They 
> say" :)  -  but I
> > haven't had time to do a lot of research into it. 
> >  
> > -----Original Message-----
> > From: Merten Schumann [mailto:[EMAIL PROTECTED]
> > Sent: 15 March 2005 5:03 
> > To: [email protected]
> > 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: [email protected]
> > 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: [email protected] 
> > 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.
> > 
> > ============================================================
> >  
> > 
> > ------------------------------------------------------------
> > 
> > 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.
> > 
> > ============================================================ 
> 
> 
> -- 
> Davanum Srinivas - http://webservices.apache.org/~dims/
> 

Reply via email to