Hi James, U can adopt ur own WS- versioning policy to overcome the effect of changing the Web service on the client.
However, here the client will have to go thru UDDI to find the appropriate Web service version to interact with. When u do some changes to the Web service , which will affect the contract (WSDL) , this will form a new TModel (as per UDDI jargon). The client will keep on interacting with the earlier WS version, since it will access thru the previous TModel key, not the latest one. I think better if u can go thru some WS-Versioning related stuff (articles, implementations etc) Regards Mahen On Mon, 25 Oct 2004 08:41:19 -0400 (EDT), James CE Johnson <[EMAIL PROTECTED]> wrote: > Lets say I have defined a Customer data object, done the java2wsdl2java > dance and now I'm using the generated Customer object in my Axis client > and server. > > Time passes and I need to remove an attribute from Customer... If I remove > the attribute and redeploy my Axis server calls from an older client (e.g. > - one which still has the now-removed attribute) will fail. > > Is there a way to evolve my server independently of the client? Or is this > just a bad idea? > >
