[ http://issues.apache.org/jira/browse/AXIS-1879?page=comments#action_12314223 ]
Merten Schumann commented on AXIS-1879: --------------------------------------- I tried the service specific flag too. What works is that the flag, if given in the service.wsdd file, get's written to server-config.wsdd in the deploy step (I tried it with nightly 1.3 build). But, still, I have to restart Axis to get xsd:string instead of soapenc:string, sorry. Thanx! 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 > Assignee: Davanum Srinivas > 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
