ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Ws Wiki] Trivial Update of "Tuscany/Scenarios" by DanMurphy
Date Wed, 17 Jan 2007 14:21:20 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:
http://wiki.apache.org/ws/Tuscany/Scenarios

------------------------------------------------------------------------------
  
  There are a number of options to solve this requirement, depending on whether the company
already has this capabilitity or if it wants to make use of a 3rd party to provide this capability.
  
+ [ExposingScenarios Exposing Scenrios];
- === Scenario 1: Expose the existing asset as-is ===
- The capability to check someones credit rating already exists in another IT system owned
by the company. The system has a programmable interface, so re-using this exisiting capabillity
makes good business sense. Further, the API is suitable to be exposed as-is as it has a simple
single operation that can be invoked in order to perform the credit check. The existing interface
is used to specify the the service interface.
  
- The interface and implementation is made available for testing / use.
+ Once the service to be used has been identified, it can be consumed by the existing application
  
- 
- === Scenario 2: Expose a modified asset ===
- The capability to check someones credit rating already exists in another IT system owned
by the company. The system has a programmable interface, so re-using this exisiting capabillity
makes good business sense. However, in order to check the persons credit rating a number of
invocation are required. The desired interface of the service is defined and used to produce
a facade template. The template is then modified to invoke the acutal API.
- 
- The interface, facard and implementation is made available for testing / use.
- 
- 
- === Scenario 3: Use a 3rd party's service as-is ===
- The company does not already have this capability (or does not want to use it). However
a third party has been found that does provide this capabillity and it has been decided that
using this service is viable. In this scenario the 3rd party makes available a service interface
to the company for use.
- 
- The interface is made available for testing / use.
- 
- 
- === Scenario 4: Use a 3rd party's service ===
- The company does not already have this capability (or does not want to use it). A third
party has been found that does provide this capabillity and it has been decided that using
this service is viable. However, the service cannot be used as-is, some additional processing
is required by the company before it can invoke the service. In this case the desired interface
is specified and this is used to produce a facarde template to the 3rd party service(s). This
template is then modified to use the 3rd party service.
- 
- The new service interface and facard are made available for testing / use.
- 

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
For additional commands, e-mail: general-help@ws.apache.org


Mime
View raw message