71Re: .NET interop issues
- Feb 12, 2001Hi Simon ,
thanks a lot .....am in the process of reading ur findings
I have a question ... here's an excerpt of ur comments :
"Here's a trace of pocketSOAP to the .NET Remoting services (not .NET
..... is there a diff b/w how .NET Remoting services and .NET
WebMethods work, esp with respect to SOAP ? Could you point me in
the right direction to find out more about the differences b/w the
Thanks for your time,
--- In soapbuilders@y..., Simon Fell <soap@z...> wrote:
> We've just been looking at inter-op with .NET, i've written up some
> results / issues at
> On Thu, 08 Feb 2001 05:00:55 -0000, in soap you wrote:
> >Hi ,
> >I was wondering if anyone has attempted to access .NET services
> >an Apache SOAP client...and if so, whether they wud care to share
> >their experiences. I've been trying to do the same, and found a
> >problems, which I also posted to the soap dev newsgroups..and
> >see alot of familiar faces here, shall not repeat that mail.
> >Noticed another thing today..I have been attempting to pass a
> >parameter to a .NET service...but it was consistently receving a
> >instead of the actually param value.
> >Used the Messaging classes to construct the payload and send it
> >across, experimented with it, and found the following:
> >a) in the original payload, the body entry for the method name was
> >similar to : <ns:sendParam xmlns:ns=blah blah> .... </ns>
> >..and the parameters inside this were not being read correctly
> >b) I modifed the above like so :
> ><sendParam .....blah blah>.... </sendParam>..
> >and voila !! it works - .NET is now being able to read the correct
> >parameters inside this...
> >what gives ????
> >To unsubscribe from this group, send an email to:
- << Previous post in topic Next post in topic >>