RE: is it possible to change soapenc:string to xsd:string in generated WSDL?
Davanum,
understand, same for me here in my stuff to process, I was just trying
to raise my feature request and bug report a bit in priority ;-) ;-) ;-)
You have this "vote" feature on JIRA, which is IMHO a suitable mechanism
to kind of set priorities and all. But nobody else seems to be
interested in my feature request, that's what I meant when I wrote
"there's no audience for this". So it's absolutely okay to be processed
not in a minute since nobody else seems to have a problem with this. :-)
Merten
> -Original Message-
> From: Davanum Srinivas [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 05, 2005 5:12 PM
> To: axis-user@ws.apache.org
> Subject: Re: is it possible to change soapenc:string to
> xsd:string in generated WSDL?
>
> Merten,
>
> we are interested in fixing this...but there just so many things to do
> and so few hours in a day :)
>
> -- dims
>
> On 5/5/05, Merten Schumann <[EMAIL PROTECTED]> wrote:
> > Clint,
> >
> > hm, I have no Axis specific code in my web service. I just wrote a
> > JAX-RPC compliant web service and added Axis to my web app
> and then let
> > Axis generate the WSDL and all for me in the deploy (wsdd)
> step. I think
> > I even did not try to write a client utilizing Axis, I just have
> >
> > But, maybe when they fix your issue my one is gone too :-)
> >
> > BTW: I tried to interest them to let the dotNetSoapEncFix to be
> > controled on a per service base (in wsdd file for a
> service) but seems
> > there's no audience for this ;-)
> > http://issues.apache.org/jira/browse/AXIS-1879
> >
> > Will have a look at this tomorrow again ..
> > cu
> > Merten
> >
> > > -----Original Message-----
> > > From: Dovholuk, Clint [mailto:[EMAIL PROTECTED]
> > > Sent: Thursday, May 05, 2005 4:45 PM
> > > To: axis-user@ws.apache.org
> > > Subject: RE: is it possible to change soapenc:string to
> > > xsd:string in generated WSDL?
> > >
> > > Merten,
> > >
> > > I've opened a bug I think that is about your issue...
> > >
> > > http://issues.apache.org/jira/browse/AXIS-1976
> > >
> > > it seems that the flag is being reset whenever you call a
> web service
> > > using the axis generated classes.
> > >
> > > to solve the issue myself, before I return anything I do:
> > >
> > > if(!TypeMappingImpl.dotnet_soapenc_bugfix)
> > > {
> > > TypeMappingImpl.dotnet_soapenc_bugfix = true; //or
> > > whichever value
> > > you "need"
> > > }
> > >
> > > it does the trick for me, but it's got to be a bug...
> > >
> > > Are you using any autogenerated classes to call some
> other web service
> > > and THEN seeing the issue?
> > >
> > > -Clint
> > >
> > >
> > >
> > > -Original Message-
> > > From: Merten Schumann [mailto:[EMAIL PROTECTED]
> > > Sent: Thursday, May 05, 2005 10:31 AM
> > > To: axis-user@ws.apache.org
> > > Subject: RE: is it possible to change soapenc:string to
> xsd:string in
> > > generated WSDL?
> > >
> > > 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: axis-user@ws.apache.org
> > > > 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 s
Re: is it possible to change soapenc:string to xsd:string in generated WSDL?
Merten,
we are interested in fixing this...but there just so many things to do
and so few hours in a day :)
-- dims
On 5/5/05, Merten Schumann <[EMAIL PROTECTED]> wrote:
> Clint,
>
> hm, I have no Axis specific code in my web service. I just wrote a
> JAX-RPC compliant web service and added Axis to my web app and then let
> Axis generate the WSDL and all for me in the deploy (wsdd) step. I think
> I even did not try to write a client utilizing Axis, I just have
>
> But, maybe when they fix your issue my one is gone too :-)
>
> BTW: I tried to interest them to let the dotNetSoapEncFix to be
> controled on a per service base (in wsdd file for a service) but seems
> there's no audience for this ;-)
> http://issues.apache.org/jira/browse/AXIS-1879
>
> Will have a look at this tomorrow again ..
> cu
>Merten
>
> > -Original Message-
> > From: Dovholuk, Clint [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, May 05, 2005 4:45 PM
> > To: axis-user@ws.apache.org
> > Subject: RE: is it possible to change soapenc:string to
> > xsd:string in generated WSDL?
> >
> > Merten,
> >
> > I've opened a bug I think that is about your issue...
> >
> > http://issues.apache.org/jira/browse/AXIS-1976
> >
> > it seems that the flag is being reset whenever you call a web service
> > using the axis generated classes.
> >
> > to solve the issue myself, before I return anything I do:
> >
> > if(!TypeMappingImpl.dotnet_soapenc_bugfix)
> > {
> > TypeMappingImpl.dotnet_soapenc_bugfix = true; //or
> > whichever value
> > you "need"
> > }
> >
> > it does the trick for me, but it's got to be a bug...
> >
> > Are you using any autogenerated classes to call some other web service
> > and THEN seeing the issue?
> >
> > -Clint
> >
> >
> >
> > -Original Message-
> > From: Merten Schumann [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, May 05, 2005 10:31 AM
> > To: axis-user@ws.apache.org
> > Subject: RE: is it possible to change soapenc:string to xsd:string in
> > generated WSDL?
> >
> > 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: axis-user@ws.apache.org
> > > 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: axis-user@ws.apache.org
> > > > 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
> > >
> >
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
RE: is it possible to change soapenc:string to xsd:string in generated WSDL?
Clint,
hm, I have no Axis specific code in my web service. I just wrote a
JAX-RPC compliant web service and added Axis to my web app and then let
Axis generate the WSDL and all for me in the deploy (wsdd) step. I think
I even did not try to write a client utilizing Axis, I just have
But, maybe when they fix your issue my one is gone too :-)
BTW: I tried to interest them to let the dotNetSoapEncFix to be
controled on a per service base (in wsdd file for a service) but seems
there's no audience for this ;-)
http://issues.apache.org/jira/browse/AXIS-1879
Will have a look at this tomorrow again ..
cu
Merten
> -Original Message-
> From: Dovholuk, Clint [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 05, 2005 4:45 PM
> To: axis-user@ws.apache.org
> Subject: RE: is it possible to change soapenc:string to
> xsd:string in generated WSDL?
>
> Merten,
>
> I've opened a bug I think that is about your issue...
>
> http://issues.apache.org/jira/browse/AXIS-1976
>
> it seems that the flag is being reset whenever you call a web service
> using the axis generated classes.
>
> to solve the issue myself, before I return anything I do:
>
> if(!TypeMappingImpl.dotnet_soapenc_bugfix)
> {
> TypeMappingImpl.dotnet_soapenc_bugfix = true; //or
> whichever value
> you "need"
> }
>
> it does the trick for me, but it's got to be a bug...
>
> Are you using any autogenerated classes to call some other web service
> and THEN seeing the issue?
>
> -Clint
>
>
>
> -Original Message-
> From: Merten Schumann [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 05, 2005 10:31 AM
> To: axis-user@ws.apache.org
> Subject: RE: is it possible to change soapenc:string to xsd:string in
> generated WSDL?
>
> 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: axis-user@ws.apache.org
> > 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: axis-user@ws.apache.org
> > > 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
> >
>
RE: is it possible to change soapenc:string to xsd:string in generated WSDL?
Merten,
I've opened a bug I think that is about your issue...
http://issues.apache.org/jira/browse/AXIS-1976
it seems that the flag is being reset whenever you call a web service
using the axis generated classes.
to solve the issue myself, before I return anything I do:
if(!TypeMappingImpl.dotnet_soapenc_bugfix)
{
TypeMappingImpl.dotnet_soapenc_bugfix = true; //or whichever value
you "need"
}
it does the trick for me, but it's got to be a bug...
Are you using any autogenerated classes to call some other web service
and THEN seeing the issue?
-Clint
-Original Message-
From: Merten Schumann [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 05, 2005 10:31 AM
To: axis-user@ws.apache.org
Subject: RE: is it possible to change soapenc:string to xsd:string in
generated WSDL?
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: axis-user@ws.apache.org
> 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: axis-user@ws.apache.org
> > 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
>
RE: is it possible to change soapenc:string to xsd:string in generated WSDL?
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: axis-user@ws.apache.org > 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: axis-user@ws.apache.org > > 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 >
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: axis-user@ws.apache.org > 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
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 > -Original Message- > From: Davanum Srinivas > Sent: Tuesday, March 15, 2005 6:29 PM > To: axis-user@ws.apache.org > 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: axis-user@ws.apache.org > > 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: 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?
RE: is it possible to change soapenc:string to xsd:string in generated WSDL?
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: axis-user@ws.apache.org > 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: axis-user@ws.apache.org > > 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: 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
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: axis-user@ws.apache.org > 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: 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. >
RE: is it possible to change soapenc:string to xsd:string in generated WSDL?
Title: RE: is it possible to change soapenc:string to xsd:string in generated WSDL?
I do know, Dino, I do know. And I do understand. And I do
agree. But have to create this VBA stuff. And I have to create the same stuff
(at the end a Excel document too) utilizing .NET too. So I just want to get both
things working. :-)
cu
Merten
From: Dino Chiesa
[mailto:[EMAIL PROTECTED] Sent: Tuesday, March 15, 2005 6:11
PMTo: axis-user@ws.apache.orgSubject: RE: is it possible
to change soapenc:string to xsd:string in generated WSDL?
Don't use MS SOAP Toolkit. It will reach end-of-life
in a month or so.
A better approach is to build a .NET webservice
client, and expose that .NET assembly via COM interop (tlbexp).
if you follow this approach, clients (your Office
docs) need the .NET Framework installed.
here's a related link
http://blogs.msdn.com/dotnetinterop/archive/2004/11/22/267933.aspx
From: Merten Schumann
[mailto:[EMAIL PROTECTED] Sent: Tuesday, March 15, 2005
12:03 PMTo: axis-user@ws.apache.orgSubject: 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
PMTo: axis-user@ws.apache.orgSubject: 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.
RE: is it possible to change soapenc:string to xsd:string in generated WSDL?
Title: RE: is it possible to change soapenc:string to xsd:string in generated WSDL?
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
PMTo: axis-user@ws.apache.orgSubject: 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: axis-user@ws.apache.orgSubject: 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 PMTo: axis-user@ws.apache.orgSubject: 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.
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 o
RE: is it possible to change soapenc:string to xsd:string in generated WSDL?
Title: RE: is it possible to change soapenc:string to xsd:string in generated WSDL? Don't use MS SOAP Toolkit. It will reach end-of-life in a month or so. A better approach is to build a .NET webservice client, and expose that .NET assembly via COM interop (tlbexp). if you follow this approach, clients (your Office docs) need the .NET Framework installed. here's a related link http://blogs.msdn.com/dotnetinterop/archive/2004/11/22/267933.aspx From: Merten Schumann [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 15, 2005 12:03 PMTo: axis-user@ws.apache.orgSubject: 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 PMTo: axis-user@ws.apache.orgSubject: 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.
RE: is it possible to change soapenc:string to xsd:string in generated WSDL?
Title: 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: axis-user@ws.apache.orgSubject: 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 PMTo: axis-user@ws.apache.orgSubject: 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. 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.
RE: is it possible to change soapenc:string to xsd:string in generated WSDL?
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
PMTo: axis-user@ws.apache.orgSubject: 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
PMTo: axis-user@ws.apache.orgSubject: 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.
RE: is it possible to change soapenc:string to xsd:string in generated WSDL?
Title: 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 PMTo: axis-user@ws.apache.orgSubject: 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.
RE: is it possible to change soapenc:string to xsd:string in generated WSDL?
Title: 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.
