🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: borland.public.cppbuilder.webservices.soap
1 messages
1 total messages Started by 24 Vitamins Thu, 19 Jul 2007 16:44
Updating an already released web-service elegantly
#95
Author: 24 Vitamins
Date: Thu, 19 Jul 2007 16:44
62 lines
2259 bytes
I have a SOAP web-service ISAPI and a client application (win32) that 
connects to it - both written in BCB6. I connect to the service in the 
client app using the WSDL Importer which creates a static binding the 
service.  I release both apps to users who end up deploying the web-service 
themselves on their own network.



In the next release I need to update the web-service with some new 
functionality and consume it from the updated client app.



What I am concerned with is the user that gets the update - installs it on 
the client and tries to use it without first updating the web-service ISAPI. 
I suspect that the client service interface will fail to even bind. Or at 
least it will throw an exception when it tries to call a function that does 
not exist.



I want to do something like this:



clientapp::Foo()

{

  bind to web-service

  if (web-service is the old one)

  {

    prompt user to update the web-service ISAPI first

    return;

  }



  // its definitely the new service

  call the new web-service function()

}





I guess I can simply wrap the binding and calling in a try catch and if 
there is a soap exception assume it is the old service - but that sucks - it 
is an assumption.



What do you suggest?

BCB 6.
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads