You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "clint dovholuk (JIRA)" <ax...@ws.apache.org> on 2005/08/29 20:51:05 UTC
[jira] Commented: (AXIS-1879) dotNetSoapEncFix flag not only for global Axis config but for per-service config too
[ http://issues.apache.org/jira/browse/AXIS-1879?page=comments#action_12320456 ]
clint dovholuk commented on AXIS-1879:
--------------------------------------
as this hasn't had action in a while, i thought i'd comment to see where the status is.
this "should be" a very simple fix and it's still not resolved.
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