Browse Prior Art Database

Process to Semi-Automate the Upgrading of a Client to Utilize Web Services Disclosure Number: IPCOM000035514D
Original Publication Date: 2005-Jan-21
Included in the Prior Art Database: 2005-Jan-21
Document File: 2 page(s) / 60K

Publishing Venue



Semi-Automated Process for Modifying Software to Use Web Services Disclosed are two variants of a semi-automated process that provide a means of upgrading software to become web services clients. As web services become available, benefits can be realized from converting existing software so that it can interact with these services, in the role of web services clients. These processes expedite and streamline the conversion of the existing software.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Process to Semi-Automate the Upgrading of a Client to Utilize Web Services

Assume a scenario where there exists a web service that provides a service for its clients. There is existing software that would benefit from becoming a client of the service. The existing software currently utilizes another means to render the function that the service provides. This could be realized for example by inline code or a subroutine or a set of classes within the software. It could also be realized from an external source, e.g. a distributed API (Application Programming Interface) such as a J2EE, CORBA or .NET implementation.

The embodiment prescribes a semi-automated process to convert the existing software such that it can become a client of the web service. The first variant uses an adapter design pattern approach. This is not invasive to the existing software, as all existing interfaces are preserved. The adapter adapts calls to the existing interface and redirects them to/from the web service. The second variant automates the refactoring of the existing software. The refactoring maps and modifies existing calls to utilize the web service. This is more invasive than the adapter approach, with more code modifications being the result. An advantage of a refactoring approach is the complete removal of the legacy API interface construct from the existing software. This positions the software better for future considerations such as responding to new versions of web services. The following steps define the two process variants for this embodiment....