Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Service Oriented Architecture Tools Platform (STP) » Updated: F2F - Use Case 3
Updated: F2F - Use Case 3 [message #373850] Thu, 15 December 2005 19:43
David Bosschaert is currently offline David BosschaertFriend
Messages: 29
Registered: July 2009
Junior Member
This use case applies to external service discovery. The external
service is (potentially) outside of your organization's control.

1. Discover remote implementation you have no control over, e.g. Web
Service, EJB, Database.
- Discovery mechanism could use functionality provided by DTP,
EMD, or other type of discovery.
output: empty external service (has name)
2. Get/derive interface
output: iFoo.wsdl/java
external service (has interface, has name)
3. Get/derive binding (e.g. another module, WSDL URL, EJB JNDI ref, etc)
(This is an optional step, it can be done post-deployment)
output: external service (has interface, has name, has binding)
4. Put into module
output: foo.module (has external)
Previous Topic:Updated: F2F - Use Case 3
Next Topic:F2F: Common Core Subproject Architecture
Goto Forum:

Current Time: Sun Jul 22 07:04:36 GMT 2018

Powered by FUDForum. Page generated in 0.01887 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top