Hi Ed, Thanx for your answer.
I had a discussion on a similar topic with a guy (Dan Rogers) on the MS newsgroups for webservices. As I understand it there was two approaches to the subject. Use Schema Extensions or add a xsd:any element to the end of the superchema (version 1). This assumes that you have schemas for both datatypes and messages. The idea is that you can replace the xsd:any with... eh.. anything..thus enabling it to be "extended". /Henrik ----- Original Message ----- From: "Ed Saltelli" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, November 18, 2004 4:04 PM Subject: RE: Best Practice > Henrik, > > No, not the only approach. It really depends on what changes you're making. > > > Most changes that I've come across have been small changes/extensions to > existing services--adding new operations or adding additional data to a > message payload. These types of changes are forward compatible with caveats > e.g. new elements are optional and not required. This change wouldn't > necessarily require a new endpoint. > > If you make massive changes you essentially have created a new service... > > Ed > > > > -----Original Message----- > From: HG [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 17, 2004 3:01 AM > To: [EMAIL PROTECTED] > Subject: Re: Best Practice > > Hi Ed > > Is this *really* the only approach? Defining it at a new endpoint? > > I mean that's what I do for know, because I can't think of any other > way...but..you know.. :-) > > Maybe this would be a task for the UDDI registry? I dunno.? Do you? Anyone? > > Regards > > Henrik > > > ----- Original Message ----- > From: "Ed Saltelli" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, November 17, 2004 5:15 AM > Subject: RE: Best Practice > > > > > > You refactor without changing the interface/WSDL to your service?! > > > > A WSDL artifact published to external consumers is a contract of sort, it > is > > not something easily changed after the fact. If you need to refactor > either > > wait for WS-Versioning (not created yet but sure to come); or create a new > > WSDL and corresponding endpoint, publish the URI, describe why it is > better, > > indicate when the old version's expiration, and hope that customers really > > use the new version. > > > > > > Ed Saltelli > > webMethods, Inc > > > > > > -----Original Message----- > > From: Jim Murphy [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, November 16, 2004 5:49 PM > > To: [EMAIL PROTECTED] > > Subject: Re: Best Practice > > > > Anand Natrajan wrote: > > > > > So what's my approach? Much as there is talk about writing WSDLs first, > I > > > prefer generating them automatically. I can do all the refactoring I > want > > in > > > my Java code and trust the java2wsdl generator to generate non-import > > WSDLs. > > > > So how do you keep you clients from breaking when you refactor? You > > must hav econtrol over both ends or *really* lenient customers. :) > > > > Jim Murphy > > Mindreef, Inc.
