Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / February 2005

Tip: Looking for answers? Try searching our database.

WSE Version of ServiceDescriptionImporter

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
GeorgeNewYork - 23 Feb 2005 22:03 GMT
I had built an engine to dynamically invoke web services by generating
web service proxy classes (on the fly).   It was built using the
framework's ServiceDescriptionImporter(). Basically, all i needed was a
wsdl url and i could create a ServiceDescription object and call the
importer to generate the source code for a proxy. I would then use
CodeDom to compile it and (voila) i had a class that could be reflected
and invoked.

That was then, this is now.

Now I am forced to upgrade to WSE and I dont see a comparable method
(one that does the work of of the command-line WseWsdl2.exe but in an
easy to swallow dll form.

I now stand perched on a rooftop ledge of a very tall building - thumb
typing this message on my blackberry.   Please do one the following (in
preferred order):

A)  Tell me there is a method(s) that exposes this functionality.
B)  Tell me i can safely redistribute the WseWsdl2.exe with my
application so that i can call it at runtime (without having MS zap me
with a laser from outer space).
C)  Tell me there is some other way without reinventing the wheel
D)  Tell my wife I loved her ;-)

George
Sami Vaaraniemi - 24 Feb 2005 10:10 GMT
>I had built an engine to dynamically invoke web services by generating
> web service proxy classes (on the fly).   It was built using the
[quoted text clipped - 20 lines]
> C)  Tell me there is some other way without reinventing the wheel
> D)  Tell my wife I loved her ;-)

If my memory serves me there isn't much difference in WSE-enabled and
non-WSE proxies other than the base class they derive from. If you've
already got the code that uses ServiceDescriptionImporter to generate a
non-WSE proxy, then to WSEfy it simply change the base class of the proxy
from System.Web.Services.Protocols.SoapHttpClientProtocol to
Microsoft.Web.Services2.WebServicesClientProtocol (and add reference to the
WSE assembly). I'm not sure if this applies to the latest version of WSE but
it's probably worth trying.

Regards,
Sami
Dilip Krishnan - 24 Feb 2005 13:54 GMT
Hello GeorgeNewYork,
     I dont see why you couldnt use the ServiceDescriptionImporter still?
Unless you are really using the WS-* stack in WSE you should be able to continue
using your technique. Now in order to be able to use policy and filters you
would need to change the type the proxy derives from to WSE's WebServicesClientProtocol,
and thats easily achievable by modifying your codedom structure.

HTH
Regards,
Dilip Krishnan
MCAD, MCSD.net
dkrishnan at geniant dot com
http://www.geniant.com

> I had built an engine to dynamically invoke web services by generating
> web service proxy classes (on the fly).   It was built using the
[quoted text clipped - 21 lines]
> D)  Tell my wife I loved her ;-)
> George

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.