[ http://issues.apache.org/jira/browse/AXIS-1879?page=comments#action_12313811 ]
Merten Schumann commented on AXIS-1879: --------------------------------------- Davanum, I gave Axis 1.2.1 a try, I think your fix is included there, at least I found it in the changelog. Well, sorry, but it seems nothing has changed. It seems, the dotNetSoapEncFix in the .wsdd is not working. At least, when I change the default in global configuration to "false" and in the .wsdd to "true", all the time the WSDL get's generated with the (wrong) soapenc:string encodings. So, it seems the parameter is not evaluated in the .wsdd. The other issue, the "blindy" reset :-), is still there: I have to restart (stop, start) my webapp to get the WSDL with the wanted xsd:string instead of soapenc:string parameter encodings. So, here nothing has changed. I don't know, maybe the reason is that I follow the approach "adding Axis to your own Webapp". Maybe it works in plain Axis, will try to test this ... Maybe I'm doing something wrong here, but I think I really used the 1.2.1 binaries ... Will check this. cu Merten > dotNetSoapEncFix flag not only for global Axis config but for per-service > config too > ------------------------------------------------------------------------------------ > > Key: AXIS-1879 > URL: http://issues.apache.org/jira/browse/AXIS-1879 > Project: Apache Axis > Type: Improvement > Components: Basic Architecture > Versions: 1.2 > Environment: not relevant here > Reporter: Merten Schumann > Priority: Minor > > The dotNetSoapEncFix flag is implemented for Axis global configuration right > now. Would be good to have this flag available for the per-service > configuration too. > It's often easier to let a user use the flag in a deploy.wsdd step than to > tell him "change your global configuration in server-config.wsdd" ... :-) > Additionally, this per-service flag would allow to decide about this dotNet > interop stuff per service and not globally. I could imagine that one day with > this global switch only you could have your old SOAP clients working but not > the newest ones 8-) > Thank you! > Merten -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
