Loading ...
Sorry, an error occurred while loading the content.

68Re: [soapbuilders] .NET interop issues

Expand Messages
  • Simon Fell
    Feb 11, 2001
      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 from
      >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 few
      >problems, which I also posted to the soap dev newsgroups..and since I
      >see alot of familiar faces here, shall not repeat that mail.
      >Noticed another thing today..I have been attempting to pass a string
      >parameter to a .NET service...but it was consistently receving a null
      >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 by .NET
      >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:
    • Show all 13 messages in this topic