Eclipse Community Forums: Service Oriented Architecture Tools Platform (STP) » Updated: F2F

Help

Home

Home » Archived » Service Oriented Architecture Tools Platform (STP) » Updated: F2F - Use Case 3

Show: Today's Messages :: Show Polls :: Message Navigator

Updated: F2F - Use Case 3 [message #373850]

Thu, 15 December 2005 19:43

David Bosschaert

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)

Report message to a moderator

Previous Topic:	Updated: F2F - Use Case 3
Next Topic:	F2F: Common Core Subproject Architecture

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 25 08:07:06 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter