[Mono-list] [Mono-dev] quick question about SOAP extension configuration

Robert Jordan robertj at gmx.net
Sat Aug 5 04:57:56 EDT 2006


L.G. Meredith wrote:
> Atsushi,
> 
> Thanks for your query. i was under the impression from a previous reply 
> that
> it was supported in mono.

It's an implemented 1.1 feature.

Robert

> 
> Best wishes,
> 
> --greg
> 
> In response to one of my earlier postings, Robert Jordan wrote:
> 
> Hey,
> 
> L.G. Meredith wrote:
>> i'm in the process of writing a gateway application. It speaks SOAP 
>> out of
>> one side of it's mouth and a proprietary network application protocol out
>> the other.
>>
>> My application would be much more beautiful and easy to maintain if i had
>> the following two bits of interface to .net/mono capability.
>>
>> 1. i want to trampoline incoming webmethods to invocations to send an
>> appropriately formatted message to a tcp stream connected to my app. That
>> is, i would like to get the current (web) method and it's arguments. i
>> would
>> prefer not to copy the incoming arguments to an invocation but to
>> generically call an api that will return a data structure providing all
> the
>> information associated with the method invocation, including method name
>> and
>> actuals (a.k.a. arguments). i can then pass this data structure to my
>> stream
>> formatter to format appropriately for the network stream.
> 
> Implement a SOAP extension:
> 
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconAlteringSOAPMessageUsingSOAPExtensions.asp 
> 
> 
> 
> 
> On 8/4/06, Atsushi Eno <atsushi at ximian.com> wrote:
>>
>> Hi,
>>
>> Just curious, isn't SOAP extension configuration new functionality
>> in .NET 2.0 which we don't support yet?
>>
>> Atsushi Eno
>>
>> L.G. Meredith wrote:
>> > All,
>> >
>> > i know this question has been asked a million times, but i can't 
>> find an
>>
>> > answer that works with my setup. Before i try it on mono, i would to
>> make
>> > sure that the SOAP extension i've implemented works on straight up 
>> .net.
>> > Everything compiles, there are no complaints about the config file. i
>> can
>> > invoke web methods and they call the code i in the main body, but no
>> SOAP
>> > extension code is executed.
>> >
>> > The SOAP extension code i've got is a simple variation on the trace
>> > extension example from the .net libraries. This compiles in with the
>> > rest of
>> > my webservice. i add the following configuration info to web.config.
>> >
>> >       <webServices>
>> >          <soapExtensionTypes>
>> >            <add type="AVSOAPIntercept.AVTraceExtension ,
>> >                     App_Code"
>> >             priority="1" group="Low" />
>> >            <add type="AVSOAPIntercept.AVTrampoline,
>> >                     App_Code"
>> >             priority="1" group="Low" />
>> >          </soapExtensionTypes>
>> >        </webServices>
>> >
>> > i have tried marking the method with
>> >
>> > [WebMethod(EnableSession=true)]
>> > [AVTrampoline]
>> > <method signature>
>> >
>> > and
>> >
>> > [WebMethod(EnableSession=true)]
>> > [AVSOAPIntercept.AVTrampoline]
>> > <method signature>
>> >
>> > i have also confirmed that if i don't put in the qualified name,
>> > AVSOAPIntercept.AVTrampoline, in the web.config extension, i get a
>> > complaint
>> > about the configuration.
>> >
>> > But, neither of these ever causes exeuction in the implementation of
>> > ProcessMessage for AVTrampoline. Any help would be greatly appreciated.
>> >
>> > Best wishes,
>> >
>> > --greg
>> >
>> >
>> > 
>> ------------------------------------------------------------------------
>> >
>> > _______________________________________________
>> > Mono-devel-list mailing list
>> > Mono-devel-list at lists.ximian.com
>> > http://lists.ximian.com/mailman/listinfo/mono-devel-list
>>
>>
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Mono-list maillist  -  Mono-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list



More information about the Mono-list mailing list