[Mono-dev] WS stack.
Atsushi Eno
atsushi at ximian.com
Mon Feb 5 01:14:21 EST 2007
Hi Daniel,
Daniel Lundqvist wrote:
> The issue here is that it always sends the oid and parentoid field
> regardless of value of <field>Specified.
> I got a patch (against SVN) for it, don't know if it's correct but
> solves the problem for me. So now it only sends oid and parentoid when
> <field>Specified is set to true. This was tested with 1.1.17.1 but the
> problem is in SVN as well from what I can see.
Oh, cool. Can you please share the patch so that it could be fixed?
> 2) When using wsdl2 from latest release of Mono I have the following issues:
> 1) When using properties for member access, and field is the same name
> as a keyword it don't prefix the property name with @.
Hmm, it would be nice if you file a bug for it. It is kind of corner
case, but fixing it would be nicer.
> 2) It seems to generate each service binding twice. One with the normal
> name and another with <name>1. I.i
> [System.Web.Services.WebServiceBinding(Name="packetfront_becs",
> Namespace="urn:packetfront_becs")]
> [System.Diagnostics.DebuggerStepThroughAttribute()]
> [System.ComponentModel.DesignerCategoryAttribute("code")]
> public class packetfront_becs :
> System.Web.Services.Protocols.SoapHttpClientProtocol {
> <snip>
> }
>
> [System.Web.Services.WebServiceBinding(Name="packetfront_becs",
> Namespace="urn:packetfront_becs")]
> [System.Diagnostics.DebuggerStepThroughAttribute()]
> [System.ComponentModel.DesignerCategoryAttribute("code")]
> public class packetfront_becs1 :
> System.Web.Services.Protocols.SoapHttpClientProtocol {
> <snip>
> }
Do you have test case for this as well? I tried it (from svn) but
it didn't happen. Though I remember this kind of duplicate results
from those days I was working on Sys.Web.Services in my private
branch. It was because of target protocol unawareness on processing
bindings.
Atsushi Eno
More information about the Mono-devel-list
mailing list