[ http://issues.apache.org/jira/browse/AXIS-1879?page=comments#action_12314221 ]
clint dovholuk commented on AXIS-1879: -------------------------------------- i have indeed tried both flags... here's a sample of my server-config.wsdd. (SNIP represents lines i cut out) <?xml version="1.0" encoding="UTF-8" ?> <deployment xmlns="http://xml.apache.org/axis/wsdd/"; xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";> <globalConfiguration> <parameter name="dotNetSoapEncFix" value="true"/> ... SNIP ... </globalConfiguration> <service name="myAxisService" provider="java:RPC"> <parameter name="dotNetSoapEncFix" value="true"/> ... SNIP ... </service> ... SNIP ... </deployment> as it stands right now, no matter how the flag is ORIGINALLY set... every single time you invoke a web service FROM axis (using ant-generated code - which in retrospect, might be the "real" issue) the flag gets reset... so i did more digging and i find that in all my ant-generated files, i get this line in all my *BindingStub.java files: ((org.apache.axis.client.Service)super.service).setTypeMappingVersion("1.2"); this line will ALWAYS BLINDLY RESET the flag... no matter what the flag is before, it ALWAYS resets this value... so i think that the REAL issue here is that the ant-generated client classes all set the type mapping version as above. is there a parameter i can pass to ant that tells it to NOT generate this line? i've commented out that single line in a few test objects and i can confirm that the removal of this line in all my "BindingStub" classes fixes this probelm of the flag getting reset. Thanks, -Clint > 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
