 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / ASP.NET / Web Services / March 2008Consistent Types Across Web Services
I am currently experiencing a problem with using web services within .Net 2.0. My problem is that i have client and server components that interact through a common class foo. This same class is used extensively through other parts of the system.When the application is distributed through web services, the web references provide an alternative class ws.foo which is quite lose but not the same. I don't really want to go through the entire application changing the types from foo to ws.foo so how do i get the web services to expose a identical type foo? Hi, This is a problam. If the problam was with two web services that expose the same type but different namespaces there is a tool you can use. You can read about it in my blog: http://kolbis.blogspot.com/ I had this problam too. I solved it using a mapper class that maps the types from the web service type to the application type. If you find another solution please share it. > I am currently experiencing a problem with using web services within .Net 2.0. > [quoted text clipped - 7 lines] > from foo to ws.foo so how do i get the web services to expose a identical > type foo? Thanks guy, i have been down the generic reflection route, but i feel that i am missing out on a trick somewhere, > Hi, > This is a problam. [quoted text clipped - 19 lines] > > from foo to ws.foo so how do i get the web services to expose a identical > > type foo? Hi Ian, This is tricky. It's actually one of the tenets of Service Orientation that Web Services share schema (i.e. the shape of the object) and not type (an implementation). However, sometimes we developers who are lucky enough to have control of both sides of the service boundary may want to reuse our classes in the way you describe. I've done the same thing in the past by generating the web service proxy myself (using WSDL.exe) and adding it to my project just like any other .cs file. Then you can simply jump in and make some gentle changes to use of foo instead of ws.foo. It's that easy. Let me know how you get on. Josh http://www.thejoyofcode.com/ Hi Josh, You are right when you say that they should share schema. However, what should you do when updating a web reference? And how can you share schema in this case? > Hi Ian, > [quoted text clipped - 14 lines] > Josh > http://www.thejoyofcode.com/ Hello again all, Yes, updating web reference is the caveat to this. If you 'update the web reference' you need to reimplement your changes. The new SchemaImporterExtension is something I've been meaning to look at for a while now and not got round to it (I wanted to enhance this to automate it such that it scans your .sln for projects with matching classes but I need to somehow get information from devenv.exe into wsdl.exe - one day :). At the end of the day it's all a trade-off, choose which one suits you. My WSDLs are designed up front so don't change too often, hence I don't mind reimplimenting a few classes here and there when they do. Josh http://www.thejoyofcode.com/ I have been down the manual wsdl route before and was trying to avoid it again. Thank for reminding me about the SOA principle, it takes the pain away slightly, i guess the thing to really do is, just like Kolbis suggests and implement a facade wrapper to really hide and abstract the entire we service implementation. Still seems a little strange as the objects were initially generated from XML schemas - i think this may be explained by subtle differences between 2003 and 2004 serialisation. Thanks anyway. > Hi Ian, > [quoted text clipped - 14 lines] > Josh > http://www.thejoyofcode.com/ you can create a component from SchemaImporterExtension class and register it on the development machine, look at this article http://www.microsoft.com/belux/nl/msdn/community/columns/jdruyts/wsproxy.mspx hth > I have been down the manual wsdl route before and was trying to avoid it again. > Thank for reminding me about the SOA principle, it takes the pain away [quoted text clipped - 26 lines] >>Josh >>http://www.thejoyofcode.com/ Hello, I have the same problem and I solved most of it by implementing my own SchemaImporterExtension class. However the only type that it doesn't work with are Typed DataSets This i a really huge problem ! Has anyone been able to solve this ? I have searched around a lot and can't seem to find any information that would solve this problem, only unanswered questions about it. ( http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=374848&SiteID=1 ) I would really appreciate any help about this. Best regards Tobias Softronic (valid MSDN subscription) > you can create a component from SchemaImporterExtension class and > register it on the development machine, look at this article [quoted text clipped - 33 lines] > >>Josh > >>http://www.thejoyofcode.com/ > Hello, > [quoted text clipped - 10 lines] > > I would really appreciate any help about this. My best advice would be to not use DataSet at all. See http://www.hanselman.com/blog/ReturningDataSetsFromWebServicesIsTheSpawnOfSatanA ndRepresentsAllThatIsTrulyEvilInTheWorld.aspx for a point of view similar to mine on the subject.  Signature-------------------------------------------------------------------------------- John Saunders | MVP - Windows Server System - Connected System Developer > > Hello, > > [quoted text clipped - 16 lines] > http://www.hanselman.com/blog/ReturningDataSetsFromWebServicesIsTheSpawnOfSatanA ndRepresentsAllThatIsTrulyEvilInTheWorld.aspx > for a point of view similar to mine on the subject. Well, thank you for your input ;-) But unfortunately, it doesn't matter how much I agree with you because I am in this situation and don't have a choice but to use Typed DataSets. Have started to write our own custom tool that "cleans" the proxy class from DataSets and inserting Using statements instead. But if anyone has any other ideas ? I would certanly like to hear about them. /Tobias
Free MagazinesGet 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 ...
|
Reply to this Message
|
 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.