Doing WebServices? Does "dotNetSoapEncFix" mean anything to you...?
Doing WebServices? Does "dotNetSoapEncFix" mean anything to you...?
- Subject: Doing WebServices? Does "dotNetSoapEncFix" mean anything to you...?
- From: Hugi Thordarson <email@hidden>
- Date: Wed, 15 Oct 2008 07:08:48 +0000
...if it does, you might be able to help me :-).
I'm in the progress of upgrading an app that provides WO WebServices
from WO 5.3 to WO 5.4, and it's been giving me some headaches. After a
bit of tinkering I've got almost everything working, except one thing:
WO 5.3 generated WSDL and SOAP responses using type="xsd:string" for
Strings, which, appparently is correct, but WO 5.4 OTOH, likes to
generate type="soapenc:string", which causes problems for some web
service consumers (specifically, those using .NET).
Google informs me that setting this property in my wsdd:
<parameter name="dotNetSoapEncFix" value="true"/>
should fix this problem - but alas, it does not. WO 5.4 still defines
Strings as "soapenc:string".
Has anyone here bumped into this?
Cheers,
- Hugi
// Hugi Thordarson
// http://hugi.karlmenn.is/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden