Q

Web service accessibility

A SearchWebServices.com member asks one of our experts "We developed an Axis document-style Web service. The time has come for a new version (WSDL evolution), but we want to keep the old one accessible at the same location. Is it possible to route the incoming request to different targets by writing a handler that could analyze the message?" Read the response or pose a question of your own.

We developed an Axis document-style Web service. The time has come for a new version (WSDL evolution), but we want to keep the old one accessible at the same location. Is it possible to route the incoming request to different targets by writing a handler that could analyze the message? And, if possible, is it a good practice?

Your handler would have to intercept the call before Axis attempts to dispatch it. Otherwise you'll get the classic "no such operation" error for one or the other version. I also don't think Axis will let you deploy two services at the same URL. You would do better to deploy an intermediary (see the Synapse project) at the original URL, and then this intermediary can route the message accordingly. Your intermediary would need to use...

the message style service. It's definitely a good practice to make upgrades as seamless as possible.

This was first published in November 2005

Dig deeper on WSDL (Web Services Description Language)

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchSoftwareQuality

SearchCloudApplications

SearchAWS

TheServerSide

SearchWinDevelopment

Close