Hello, just tried Axis 1.2 final instead of 1.2rc3. My web services still work fine :-)
Found that the param "dotNetSoapEncFix" in server-config.wsdd obviously made it to the final 1.2 That's fine for my usage scenario. Seems, by default it's set to "true". Anyway, I still have these strange behaviour with freshly deployed services, see below ... Again, anybody else experiencing this strange behaviour in Axis? Maybe it's just my usage scenario here with Tomcat in a Windows environment or so ... cu Merten > -----Original Message----- > From: Merten Schumann [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 13, 2005 5:19 PM > To: [email protected] > Subject: RE: is it possible to change soapenc:string to > xsd:string in generated WSDL? > > Hello, > > I'm playing around with this dotNetSoapEncFix in Axis. It > works fine so > far, I have xsd:string instead of soapenc:string in my generated WSDL. > But for rpc/enc web services, it works a bit funny: when I deploy my > service and look at the WSDL, there are these soapenc:string beasts > contained. I have to stop/start my web app (containing Axis), when I > then retrieve the WSDL again (I do not undeploy/deploy my service > again), it's correctly containing the xsd:string stuff. This "feature" > works each time when I deploy my service for the first time ... It > seems, for rpc/lit and doc/lit this issue doesn't appear. > > Anybody else experiencing this strange behaviour in Axis??? > > cu > Merten > > > -----Original Message----- > > From: Merten Schumann [mailto:[EMAIL PROTECTED] > > Sent: Friday, March 18, 2005 10:19 AM > > To: [email protected] > > Subject: RE: is it possible to change soapenc:string to > > xsd:string in generated WSDL? > > > > as suggested, created an enhancement request > > http://issues.apache.org/jira/browse/AXIS-1879 :-) > > > > cu > > Merten >
