[Mono-dev] SOAPAction

[Atsushi Eno]

Hi,

I'm no remoting expert so I don't know the answer, but SOAP
frameworks are not always interoperable for each. Even
sys.web.services and wcf do not interoperate together, unless
applications are designed to do.
Sys.web.services and remoting have different message serialization
scheme, so it does not always sound like a bug if they do not
interoperate.

Atsushi Eno

Jerry Haltom wrote:
> Would this be because of my use of Activator? I am in fact using
> Activator on the client side.
> 
> You are right. Switching to wsdl2 generated proxies solves the problem.
> So, is this simply a bug in what Activator generates? I had thought this
> was supposed to work. I will try it on Windows when I get into the
> office later.
> 
> On Tue, 2007-04-17 at 16:04 +0900, Atsushi Eno wrote:
>> I doubt. The stack trace starts from
>> System.Runtime.Serialization.Formatters.Soap/System.Runtime.Serialization.Formatters.Soap/SoapTypeMapper.cs:435
>>
>> So, you are either mixing different things, or providing insufficient
>> information on what you are doing.
>>
>> Atsushi Eno
>>
>> Jerry Haltom wrote:
>>> Tried to explain it pretty well up front. Simple web service. Using
>>> a .asmx file. Not using remoting.
>>>
>>> On Tue, 2007-04-17 at 15:24 +0900, Atsushi Eno wrote:
>>>> Jerry Haltom wrote:
>>>>> Having a problem using a XSP2 web service from a Mono client on the
>>>> same machine. Simply trying a very simple test case. Building a .asmx
>>>> file, using Activator.GetObject(Type, string) on the client. Single
>>>> method on the server `int Foo(int i)`. 
>>> _______________________________________________
>>> Mono-devel-list mailing list
>>> Mono-devel-list at lists.ximian.com
>>> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>>
> 
>