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 "Davanum Srinivas (JIRA)" <ax...@ws.apache.org> on 2007/09/28 14:53:54 UTC
[jira] Updated: (AXIS-1879) dotNetSoapEncFix flag not only for
global Axis config but for per-service config too
[ https://issues.apache.org/jira/browse/AXIS-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS-1879:
-----------------------------------
Assignee: (was: Davanum Srinivas)
> dotNetSoapEncFix flag not only for global Axis config but for per-service config too
> ------------------------------------------------------------------------------------
>
> Key: AXIS-1879
> URL: https://issues.apache.org/jira/browse/AXIS-1879
> Project: Axis
> Issue Type: Improvement
> Components: Basic Architecture
> Affects 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org