[
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
