Re: Some questions on what technology to use

From: Softwaremaker (msdn_at_removethis.softwaremaker.net)
Date: 03/04/04 

Date: Fri, 5 Mar 2004 04:50:15 +0800

Hi,

What exactly are you using WSE for ? It seems like all you need is to
generate a WSDL around an assembly. WSE is for WS-Routing, WS-Security, DIME
and others.

.NET Assemblies are meta-data and are therefore self-describing. VS.NET can
easily create the WSDL to your web service methods.

http://www.roguewave.com/developer/tac/examples/leif/LEIFClient_dotNetService/html/7-2.html

hth 

-- 
Thank you very much
Warmest Regards,
William T (Willie) - Softwaremaker
Architect | Evangelist | Consultant
Microsoft Regional Director
http://www.microsoft.com/rd
+++++++++++++++++++++++++++++++++
"Lee Alexander" <leea@_no_spam_please_pobox.com> wrote in message
news:eubj9diAEHA.1732@TK2MSFTNGP12.phx.gbl...
> > <Quote>I am sorry I am kinda lost here. Are you looking for a tool to
> > automate the gerneration of the WSDL. There is no need to use WSE for
> this.
> > .NET comes with a tool called the WSDL.exe that generates the WSDL for
> you.
> What I mean is under WSE if I derive from SoapService or SoapReceiver and
> process the messages from a handling member how will WSDL.exe or VS.NET
know
> that say the "add" message expects two parameters and returns the result
> just by looking at MyService::MyMessageHandler below. I can't see how it
> would be able to deduce this if the signature of the method is simply:
>
> class MyService: SoapService
> {
>   [SoapMessage[urn:math:add]]
>   SoapEnvelope MyMessageHandler( SoapEnvelope message )
>   {
>       // process message
>   }
> }
>
> I guess I must be missing something.. Also like I said in the original
> message it would be nice to bind a message directly to a member method of
a
> class and the message parameters marshalled to the members relevent
> parameter.
>
> I've been reading the following article below as a basis for my
> understanding of how you would go about creating a web service using wse
2.0
>
> http://msdn.microsoft.com/msdnmag/issues/03/09/XMLFiles/default.aspx
>
>
> Thanks for your help...
>
>
> Regards
> Lee
>
>
>
> "Softwaremaker" <msdn@removethis.softwaremaker.net> wrote in message
> news:ej6Ao1gAEHA.3220@TK2MSFTNGP10.phx.gbl...
> > Hi, please see comments below.
> >
> > -- 
> > Thank you very much
> >
> > Warmest Regards,
> > William T (Willie) - Softwaremaker
> > Architect | Evangelist | Consultant
> >
> > Microsoft Regional Director
> > http://www.microsoft.com/rd
> >
> > +++++++++++++++++++++++++++++++++
> >
> > "Lee Alexander" <lee@NoSpamPlease_Digita.com> wrote in message
> > news:OntgZmgAEHA.212@TK2MSFTNGP12.phx.gbl...
> > > I am new to Web Services and am trying to get over that feeling of
being
> > > slightly lost in a foreign place so to speak. I have a few questions:
> > >
> > > What technology should I be looking at with regards to implementing a
> web
> > > service under dot net?
> >
> > <Quote>If you implement a WS under .Net, you are using .Net as the
> > implementing technology ;)</Quote>
> >
> > I know this is a pretty open ended question but what
> > > I'm looking for is a technology that will see me in good stead for the
> > > future whilst being rooted in the *near* future to present. I have had
a
> > > look at Web Services using remoting and also WSE 2. I'm not currently
> > > looking at ASMX as one of my restrictions is that the web service
should
> > > potentially be independent from a web server like IIS. I get the
> > impression
> > > from postings that remoting is probably the wrong way to go as I might
> > have
> > > upgrade problems when Indigo comes out; yet it seems the simplest in
> terms
> > > of attaching messages to methods and automatically generating WSDL
etc..
> > > Thoughts on this?
> >
> > <Quote>To fully maximize the power and speed of Remoting, its best to
use
> > the Binary Formatter. If you choose to use the SOAP Formatter, be aware
> that
> > .NET generates its own proprietary version of the WSDL.</Quote>
> >
> > >
> > > I have had a look at WSE 2.0 and it seems more difficult to generate a
> > WSDL
> > > file (if not impossible)  since there isn't such a tight mapping
between
> > the
> > > message handler and the message structure. Lets say I have a message
> > called
> > > Add that takes two parameters and returns the result. From what I have
> > read
> > > for WSE I would derive from SoapReciever and override the Receive
> message
> > > manually drilling into the envelopes body using XPath when the message
> > > arrived. Another alternative would be to use SoapService which gives
me
> a
> > > little extra help by routing the message to a declared method; but the
> > > declared method would still be of the form:
> > >
> > >  SoapEnvelope MyMessageHandler( SoapEnvelope message )
> > > {
> > >     // process message
> > > }
> > >
> > > So I would still have to get down and dirty with some XML.
> >
> > <Quote>I am sorry I am kinda lost here. Are you looking for a tool to
> > automate the gerneration of the WSDL. There is no need to use WSE for
> this.
> > .NET comes with a tool called the WSDL.exe that generates the WSDL for
> you.
> > If you use VS.NET as the IDE, VS.NET will generate a WSDL wrapper
aropund
> > the assembly you create. So there is really no need to get into the XML
> > inner plumbings of WSDL.</Quote>
> >
> > >
> > > So my question here is if I use either of these ways to handle the
> message
> > > presumably there would be no way of *automatically* generating the
WSDL;
> > so
> > > I would have to create the WSDL manually, is that correct or am I
> missing
> > > something obvious here? If this is the case will there be (in the
> future)
> > a
> > > more closely coupled link between the message handler and the message
> > format
> > > like say:
> > >
> > > [SoapMessage[urn:math:add]]
> > > int Add( int x, int y )
> > > {
> > >     return x + y;
> > > }
> > >
> > > This would remove the hassle of having to drill into the XML to get my
> > > parameters etc.
> >
> > <Quote>I am sorry I am kinda lost here. Are you looking for a tool to
> > automate the gerneration of the WSDL. There is no need to use WSE for
> this.
> > .NET comes with a tool called the WSDL.exe that generates the WSDL for
> you.
> > If you use VS.NET as the IDE, VS.NET will generate a WSDL wrapper
aropund
> > the assembly you create. So there is really no need to get into the XML
> > inner plumbings of WSDL.</Quote>
> >
> > >
> > > My next stop will be looking at Indigo so how does this fit with where
> I'm
> > > trying to go?
> > >
> > > Any help/thoughts would be much appreciated...
> > >
> > > Regards
> > > Lee
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: Some questions on what technology to use
    ... WSE is for WS-Routing, WS-Security, DIME ... .NET Assemblies are meta-data and are therefore self-describing. ... easily create the WSDL to your web service methods. ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Some questions on what technology to use
    ... > automate the gerneration of the WSDL. ... What I mean is under WSE if I derive from SoapService or SoapReceiver and ... understanding of how you would go about creating a web service using wse 2.0 ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Some questions on what technology to use
    ... > automate the gerneration of the WSDL. ... What I mean is under WSE if I derive from SoapService or SoapReceiver and ... understanding of how you would go about creating a web service using wse 2.0 ...
    (microsoft.public.dotnet.framework)
  • Re: Some questions on what technology to use
    ... > look at Web Services using remoting and also WSE 2. ... > of attaching messages to methods and automatically generating WSDL etc.. ... So there is really no need to get into the XML ...
    (microsoft.public.dotnet.framework)
  • Re: Some questions on what technology to use
    ... > look at Web Services using remoting and also WSE 2. ... > of attaching messages to methods and automatically generating WSDL etc.. ... So there is really no need to get into the XML ...
    (microsoft.public.dotnet.framework.webservices)
Loading