Re: Web Service Versions
From: BjörnHolmberg (bjRemovethiSorn.holmberg_at_suliteAndthiSlma.com)
Date: 07/31/04
- Next message: J. L. Goddard: "Passing a Null to Web Method"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 31 Jul 2004 20:07:27 GMT
Hello Shaji!
Seems that .net proxies does not perform a validation against the wsdl (and xsd)
found at the webservice endpoint. Because of this it's possible to add new
functionality without breaking existing clients. If you need a more formal
approach, check up on Programming .NET Components by Juval Löwy. The ideas you
might need are in appendix A. The corresponding code example "Interface-based
web services" can be found at: http://www.idesign.net.
Regards
Bjorn
Shaji Sethu wrote:
> Richard Thombs wrote:
> > I ended up tagging my .asmx files with a 'Vx' suffix, so I have
> > TeamHavenMobileV1.asmx, TeamHavenMobileV2.asmx etc, etc.
> >
> > Each new version started off as a direct copy of the code and then code
> > modified to add whatever new methods I wanted, thus ensuring that the old
> > service remained untouched.
> >
> > R.
> Thanks Richard to your response. The issue i have is that I approached
> web service from a different angle. Instead of creating a class and then
> exposing it as a web service I created all the schemas (xsd) and then
> manually create a WSDL and finally created a server stub from this to
> make the web service. In this approach the change management is highly
> dependent on the XML schemas and if I take the normal approach and
> version the schemas using namespace it breaks backward
> compatibailty.....so kind on in a roack and hard place and need a
> lateral thought to get out of this.
>
> /Shaji
- Next message: J. L. Goddard: "Passing a Null to Web Method"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
