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 "Merten Schumann (JIRA)" <ax...@ws.apache.org> on 2005/03/16 08:55:20 UTC
[jira] Created: (AXIS-1879) dotNetSoapEncFix flag not only for global Axis config but for per-service config too
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: 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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1879) dotNetSoapEncFix flag not only for global Axis config but for per-service config too
Posted by "clint dovholuk (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1879?page=comments#action_12314222 ]
clint dovholuk commented on AXIS-1879:
--------------------------------------
also as a post comment:
i found the typemappingversion flag in the ant call to set... i *could* use 1.1 and then the flag will ALWAYS be set to true... but i still believe this represents a bug in axis. even if i "blindly" set it to true, if i have a service that i do NOT want the flag to be true on, any time i call my BindingStub class it'll be reset no matter what again.
hope that makes sense.
-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
[jira] Commented: (AXIS-1879) dotNetSoapEncFix flag not only for global Axis config but for per-service config too
Posted by "Merten Schumann (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1879?page=comments#action_12315819 ]
Merten Schumann commented on AXIS-1879:
---------------------------------------
Dims,
could you tell if you could reproduce the problem at least? I mean, that you need to stop/start a "webapp with Axis added" before xsd:string instead of soapenc:string gets generated to the WSDL? It's really not a showstopper, but it's not nice for me, I have to force users of my web service after the deploy step to restart my webapp :-)
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
[jira] Reopened: (AXIS-1879) dotNetSoapEncFix flag not only for global Axis config but for per-service config too
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1879?page=all ]
Davanum Srinivas reopened AXIS-1879:
------------------------------------
Assign To: Davanum Srinivas
> 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
[jira] Commented: (AXIS-1879) dotNetSoapEncFix flag not only for
global Axis config but for per-service config too
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXIS-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531256 ]
Davanum Srinivas commented on AXIS-1879:
----------------------------------------
Merten,
*was* active...
-- dims
> 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
[jira] Updated: (AXIS-1879) dotNetSoapEncFix flag not only for
global Axis config but for per-service config too
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ 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
[jira] Commented: (AXIS-1879) dotNetSoapEncFix flag not only for global Axis config but for per-service config too
Posted by "Merten Schumann (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1879?page=comments#action_64615 ]
Merten Schumann commented on AXIS-1879:
---------------------------------------
In Axis 1.2 final this dotNetSoapEncFix flag is set by default to true in server-config.wsdd.
That's good for my usage scenario. So if there should be really problems to implement the flag on a per service base, I would draw back my feature request. I mean, I could write to my documentation for the users of my web service "just do not change the default in Axis 1.2 for the dotNetSoapEncFix".
> 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: 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
[jira] Commented: (AXIS-1879) dotNetSoapEncFix flag not only for global Axis config but for per-service config too
Posted by "Merten Schumann (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1879?page=comments#action_12314201 ]
Merten Schumann commented on AXIS-1879:
---------------------------------------
well, if the code is not in 1.2.1 but only the changelog entry, that would explain why it's not working :-)
Just tried the nightly 1.3 build. Well, sorry, I still have to stop/start my webapp to get the WSDL generated correctly with the needed xsd:string instead of soapenc:string ...
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
[jira] Commented: (AXIS-1879) dotNetSoapEncFix flag not only for
global Axis config but for per-service config too
Posted by "Merten Schumann (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXIS-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531003 ]
Merten Schumann commented on AXIS-1879:
---------------------------------------
aha, Dims, still active here, good :-)
Have to admit, haven't followed development of Axis since 2005 :-(
will do it the next days ...
> 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
[jira] Commented: (AXIS-1879) dotNetSoapEncFix flag not only for global Axis config but for per-service config too
Posted by "Merten Schumann (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1879?page=comments#action_12313811 ]
Merten Schumann commented on AXIS-1879:
---------------------------------------
Davanum,
I gave Axis 1.2.1 a try, I think your fix is included there, at least I found it in the changelog. Well, sorry, but it seems nothing has changed.
It seems, the dotNetSoapEncFix in the .wsdd is not working. At least, when I change the default in global configuration to "false" and in the .wsdd to "true", all the time the WSDL get's generated with the (wrong) soapenc:string encodings. So, it seems the parameter is not evaluated in the .wsdd.
The other issue, the "blindy" reset :-), is still there: I have to restart (stop, start) my webapp to get the WSDL with the wanted xsd:string instead of soapenc:string parameter encodings. So, here nothing has changed.
I don't know, maybe the reason is that I follow the approach "adding Axis to your own Webapp". Maybe it works in plain Axis, will try to test this ...
Maybe I'm doing something wrong here, but I think I really used the 1.2.1 binaries ... Will check this.
cu
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
> 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
[jira] Commented: (AXIS-1879) dotNetSoapEncFix flag not only for global Axis config but for per-service config too
Posted by "clint dovholuk (JIRA)" <ax...@ws.apache.org>.
[ 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
[jira] Resolved: (AXIS-1879) dotNetSoapEncFix flag not only for global Axis config but for per-service config too
Posted by "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
[jira] Commented: (AXIS-1879) dotNetSoapEncFix flag not only for global Axis config but for per-service config too
Posted by "clint dovholuk (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1879?page=comments#action_12314179 ]
clint dovholuk commented on AXIS-1879:
--------------------------------------
NOTE: pardon me if it's bad ettiquitte, but there's still two bugs open referencing the "same topic" so i posted twice (clint)
hi dims,
sorry for the slow turnaround... i tried out 1.2.1 and i don't think your fix made it to the release...
i grepped through the source using:
grep -rin "TypeMappingImpl.dotnet_soapenc_bugfix" ./*
at
src/org/apache/axis
and i found four results:
./AxisEngine.java:191: TypeMappingImpl.dotnet_soapenc_bugfix = true;
./encoding/TypeMappingImpl.java:612: return TypeMappingImpl.dotnet_soapenc_bugfix;
./encoding/TypeMappingRegistryImpl.java:297: TypeMappingImpl.dotnet_soapenc_bugfix = false;
./encoding/TypeMappingRegistryImpl.java:300: TypeMappingImpl.dotnet_soapenc_bugfix = true;
so i looked at the code... here's what i see:
- AxisEngine "correctly" sets TypeMappingImpl.dotnet_soapenc_bugfix to true based on the property
- i don't see where TypeMappingImpl.dotnet_soapenc_bugfix gets set in TypeMappingImpl
- TypeMappingRegistryImpl BLINDLY still resets the flag depending on version number (as per my original bug)
i don't think the fix is either in 1.2.1 or i'm missing something...
-Clint
P.S. the flag is (obviously?) :) still getting reset for me and i still need to manually remember to reset the flag after every call to my .net client...
> 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
[jira] Commented: (AXIS-1879) dotNetSoapEncFix flag not only for global Axis config but for per-service config too
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1879?page=comments#action_12314219 ]
Davanum Srinivas commented on AXIS-1879:
----------------------------------------
Did you try adding
<parameter name="dotNetSoapEncFix" value="true"/>
UNDER the <service> element in your server-config.wsdd? Please see the commit (http://marc.theaimsgroup.com/?l=axis-dev&m=111863133912965&w=2). we now pick up the setting from service too.
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
> 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
[jira] Commented: (AXIS-1879) dotNetSoapEncFix flag not only for global Axis config but for per-service config too
Posted by "Merten Schumann (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1879?page=comments#action_12313801 ]
Merten Schumann commented on AXIS-1879:
---------------------------------------
sounds good, will try things out later the day and respond again, thanx a lot for now
> 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
[jira] Commented: (AXIS-1879) dotNetSoapEncFix flag not only for global Axis config but for per-service config too
Posted by "clint dovholuk (JIRA)" <ax...@ws.apache.org>.
[ 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
[jira] Commented: (AXIS-1879) dotNetSoapEncFix flag not only for global Axis config but for per-service config too
Posted by "Merten Schumann (JIRA)" <ax...@ws.apache.org>.
[ 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
[jira] Commented: (AXIS-1879) dotNetSoapEncFix flag not only for global Axis config but for per-service config too
Posted by "clint dovholuk (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1879?page=comments#action_12314225 ]
clint dovholuk commented on AXIS-1879:
--------------------------------------
I tried using the ant wsdl2java task. Here's what my target looks like:
<target name="generateObjects">
<antcall target="wsdl2java">
<param name="typeMappingVersion" value="1.1"/>
<param name="param.endpoint.wsdl" value="http://{URL to .NET service}.asmx?wsdl" />
<param name="param.java.package" value="{package}" />
</antcall>
</target>
it still generates : ((org.apache.axis.client.Service)super.service).setTypeMappingVersion("1.2");
should i start up a new bug for this issue or do you think it's "related"?
Thanks again,
-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
[jira] Commented: (AXIS-1879) dotNetSoapEncFix flag not only for global Axis config but for per-service config too
Posted by "Merten Schumann (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-1879?page=comments#action_12320545 ]
Merten Schumann commented on AXIS-1879:
---------------------------------------
YES, would be nice to have :-)
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