ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Ws Wiki] Update of "Tuscany/Scenarios" by DanMurphy
Date Wed, 17 Jan 2007 11:47:39 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.

The following page has been changed by DanMurphy:

New page:
=Tuscany Scenarios=
"Following discussions on dev, here is an first bash at some scenarios"
==Enable an existing asset==
A valuable existing piece of functionality exists in CPP, Java or PHP. This functionality
is required, or soon will be, by another system and properly others in the future. To make
it easier to reuse this capability it has been decided to expose this functionality as a service.
A well deigned service interface is produced. The interface may be identical to that of the
existing asset, or may be based on a standard. In the case of a standard, a facade will be
required such that the existing assets interface is wrapped to conform to the desired standard.
As a result, the component is ready to be deployed for consumption.
The motivation behind this is that there are tried and trusted existing IT assets. Exposing
these should reduce cost, risk, redundancy and elapsed time.
"What about existing assets that are not CPP or Java, eg. JavaScript? Should existing include
a facade, or is this a new service ?"
==Create a new service==
A requirement has been identified for a new service that does not exist. This service is not
available, or acceptable, from a third party, so it has been decided to develop the new service
from scratch. The new service may make use of other services.
*Use a service to provide functionality
A service exists that is required to provide a capability to either a new or existing system.
*Change the selected service implementation

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message