[jira] Resolved: (AXIS-1879) dotNetSoapEncFix flag not only for global Axis config but for per-service config too

["Davanum Srinivas (JIRA)" <ax...@ws.apache.org>]

     [ http://issues.apache.org/jira/browse/AXIS-1879?page=all ]
     
Davanum Srinivas resolved AXIS-1879:
------------------------------------

    Resolution: Fixed

Checked in a Possible fix for AXIS-1976 - dotnet_soapenc_bugfix is "blindly" reset
which is a also a Fix for AXIS-1879 - dotNetSoapEncFix flag not only for global Axis config but for per-service config too

Notes:
- Now you can specify the following inside a service as well in your wsdd.
<parameter name="dotNetSoapEncFix" value="true"/>
- Service specific setting trumps the global setting.

So just set the dotNetSoapEncFix on for all the services that are consumed by dot net and you should be all set. 

Please try latest CVS or the latest nightly and let me know if this takes care of your problem.

thanks,
dims

> 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