|
|
You're in the
dotnet web services
group:Consistent Types Across Web Services
dotnet 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
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. [quoted text, click to view] "IanH" wrote:
> 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
Thanks guy, i have been down the generic reflection route, but i feel that i
am missing out on a trick somewhere, [quoted text, click to view] "Kolbis Guy" wrote:
> 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. > > "IanH" wrote: > > > 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
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? [quoted text, click to view] "Josh Twist" wrote:
> 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/ >
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. [quoted text, click to view] "Josh Twist" wrote:
> 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/ >
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 [quoted text, click to view] IanH wrote:
> 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. > > "Josh Twist" wrote: > > >>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/ >>
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/
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) [quoted text, click to view] "Ashish" wrote:
> 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 > > > > > IanH wrote: > > 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. > > > > "Josh Twist" wrote: > > > > > >>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/ > >> > >>
[quoted text, click to view]
"Tobias" <Tobias@discussions.microsoft.com> wrote in message news:996DBFBA-329D-4DE9-86C4-39AC2CF2BEFF@microsoft.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. My best advice would be to not use DataSet at all. See http://www.hanselman.com/blog/ReturningDataSetsFromWebServicesIsTheSpawnOfSatanAndRepresentsAllThatIsTrulyEvilInTheWorld.aspx for a point of view similar to mine on the subject. -- -------------------------------------------------------------------------------- John Saunders | MVP - Windows Server System - Connected System Developer
[quoted text, click to view]
"John Saunders [MVP]" wrote: > "Tobias" <Tobias@discussions.microsoft.com> wrote in message > news:996DBFBA-329D-4DE9-86C4-39AC2CF2BEFF@microsoft.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. > > My best advice would be to not use DataSet at all. > > See > http://www.hanselman.com/blog/ReturningDataSetsFromWebServicesIsTheSpawnOfSatanAndRepresentsAllThatIsTrulyEvilInTheWorld.aspx > for a point of view similar to mine on the subject. > -- > -------------------------------------------------------------------------------- > John Saunders | MVP - Windows Server System - Connected System Developer > > 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.
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |