Query on typing SoapService methods : Prev: Confused WS, SOA
From: Jules (Roseanna80_at_hotmail.com)
Date: 09/30/04
- Next message: Sumaira Ahmad: "Authenticate UsernameToken against Active Directory"
- Previous message: DotNetFan_at_Community.nospam: "Re: Thread Pooling when using SoapService & SoapClient"
- Next in thread: Hervey Wilson [MSFT]: "Re: Query on typing SoapService methods : Prev: Confused WS, SOA"
- Reply: Hervey Wilson [MSFT]: "Re: Query on typing SoapService methods : Prev: Confused WS, SOA"
- Reply: Jules: "Re: Query on typing SoapService methods : Prev: Confused WS, SOA"
- Messages sorted by: [ date ] [ thread ]
Date: 30 Sep 2004 16:47:48 -0700
Hervey
Many thanks for your helpful posts,and introducing me to this cool
stuff.
As you recommended using SoapService and [SoapMethod]s, instead of
SoapReceiver, does now allow me to query Myservice.ashx?wsdl to return
my wsdl desription. I can also Add Web Reference from visual studio
client, on another machine to create some proxy code classes.
However, my wsdl on my initial attempts so far seems to have generated
rather loosely type message types such that my SoapService method:
public void AcceptSubscription(SoapEnvelope env)
becomes to following Wsdl:
<s:complexType name="AnySchema">
<s:sequence>
<s:any minOccurs="0" maxOccurs="unbounded"
processContents="lax" />
</s:sequence>
<message name="AcceptSubscriptionMessageIn">
<part name="data" type="s0:AnySchema" />
</message>
Which in the (VS Add Web Reference) proxy generated becomes
AcceptSubscription(XMLElement[] data)
I am not quite sure how these proxy methods are really helping me,
beyond simply using SoapClient. I have been reading various MSDN WSE
articles, and I need to read and understand a lot more on how I can
specify my SOA services acros the Internet to third parties. My
feeling is that simply receiving SoapEnvelope, cannot in itself help
define any types. Since it is a message after all, and not a parameter
list. So I guess this means that when I go towards SOA message based
paradigm, which consists of exchanging Soap envelopes, I have do more
of my own specification of what my 'services do'. I cannot really rely
upon auto generated wsdl, to specify my services, and I do need to
provide explicit support to my client developers as to what my
services are doing to their soap bodies.
I guess I have become rather lazy with the Microsoft web service RPC
based paradigm, where I can simply browse for a remote service, Add
Web Reference and develop Client code against generated tightly typed
proxy methods. Which is sort of where I would really like to be with
SOA messaging.
Many Thanks for helping me understand WSE and SOAP processing.
Jules
"Hervey Wilson [MSFT]" <herveyw.nospam@nospam.microsoft.com> wrote in message news:<OKZ0AeppEHA.1816@TK2MSFTNGP09.phx.gbl>...
> Jules wrote:
> > Many Thanks Hervey
> >
> > Another query is how I can wsdl query a WebHandler based service,
> > based upon ashx files. I had hoped that I could still ?wsdl, or use
> > Add Web Reference against ashx file, but its only expecting asmx
> > files. Which is a shame, because discovering http services and
> > SoapReceiver message level is the desirable combination. Am I missing
> > something.
> >
>
> SoapReceiver itself does not directly produce WSDL output, however
> SoapService can generate this automatically. You can override the
> GetDescription method on SoapReceiver to return a WSDL document if you
> need to.
>
> The WseWsdl2 command line tool in the product can issue the ?WSDL query
> to these services and generate a WSE-enabled proxy for them. This should
> work on all transports in the product.
- Next message: Sumaira Ahmad: "Authenticate UsernameToken against Active Directory"
- Previous message: DotNetFan_at_Community.nospam: "Re: Thread Pooling when using SoapService & SoapClient"
- Next in thread: Hervey Wilson [MSFT]: "Re: Query on typing SoapService methods : Prev: Confused WS, SOA"
- Reply: Hervey Wilson [MSFT]: "Re: Query on typing SoapService methods : Prev: Confused WS, SOA"
- Reply: Jules: "Re: Query on typing SoapService methods : Prev: Confused WS, SOA"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|