Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Swordfish Documentation: Architecture"

(Design of Interceptor Framework)
Line 6: Line 6:
 
For an introduction, see Whitepaper: [http://www.eclipse.org/swordfish/assets/whitepaper.pdf Eclipse Swordfish – an Open Source SOA Runtime Framework for the Enterprise] (February 2009)
 
For an introduction, see Whitepaper: [http://www.eclipse.org/swordfish/assets/whitepaper.pdf Eclipse Swordfish – an Open Source SOA Runtime Framework for the Enterprise] (February 2009)
  
== Component Architecture for the Service Registry Plugin ==
+
 
 +
== Component Architectures ==
 +
=== Service Registry Plugin ===
 
Swordfish supports the connection to different service registries in order to allow [[Swordfish_Documentation:_Architecture:_Dynamic_Endpoint_Resolution | dynamic endpoint resolution]]. This flexibility is realized through the service registry plugin.
 
Swordfish supports the connection to different service registries in order to allow [[Swordfish_Documentation:_Architecture:_Dynamic_Endpoint_Resolution | dynamic endpoint resolution]]. This flexibility is realized through the service registry plugin.
 
<br/>
 
<br/>
  
== Component Architecture for the Policy Trading Plugin ==
+
=== Policy Trading Plugin ===
 
Swordfish shall support flexible support for policy trading at service resolution. This includes selection of a suitable service provider based on a consumer policy and trading of an agreed policy for service invocation.
 
Swordfish shall support flexible support for policy trading at service resolution. This includes selection of a suitable service provider based on a consumer policy and trading of an agreed policy for service invocation.
 
Here the team provides sketches of the component architecture of an exemplary implementation [[Swordfish_Documentation:_Architecture:_Policy_Trading_Plugin | Policy Trading Plugin]].
 
Here the team provides sketches of the component architecture of an exemplary implementation [[Swordfish_Documentation:_Architecture:_Policy_Trading_Plugin | Policy Trading Plugin]].
  
== Component Architecture for the Internal Service Proxy Plugin ==
+
=== Internal Service Proxy Plugin ===
 
[[Swordfish_Documentation:_Architecture:_Internal_Service_Proxy | Internal Service Proxy]].
 
[[Swordfish_Documentation:_Architecture:_Internal_Service_Proxy | Internal Service Proxy]].
  
== Design of Interceptor Framework ==
+
=== Interceptor Framework ===
 
The [[Swordfish_Documentation:_Architecture:_Interceptor_Framework | Interceptor Framework]] provides generic support for intercepting messages in different stages of the communication between consumer and provider. It enables implementations that allow the distinguishing role (consumer / provider) and scope (request, response).
 
The [[Swordfish_Documentation:_Architecture:_Interceptor_Framework | Interceptor Framework]] provides generic support for intercepting messages in different stages of the communication between consumer and provider. It enables implementations that allow the distinguishing role (consumer / provider) and scope (request, response).
  
== Component Architecture for the Technical Parameter Propagation ==
+
=== Technical Parameter Propagation ===
 
[[Swordfish_Documentation:_Architecture:_Parameter_Propagation | Technical Parameter Propagation]].
 
[[Swordfish_Documentation:_Architecture:_Parameter_Propagation | Technical Parameter Propagation]].
  
Line 28: Line 30:
  
  
----------------------------
+
----
 
[[Swordfish | Swordfish Wiki Home]]
 
[[Swordfish | Swordfish Wiki Home]]

Revision as of 05:09, 20 November 2009

{{#eclipseproject:rt.swordfish}}

This page provides the entry point for architectural concepts and corresponding discussions.
Note: The information provided here is dynamic and is meant to reflect the current status of the project discussion.

For an introduction, see Whitepaper: Eclipse Swordfish – an Open Source SOA Runtime Framework for the Enterprise (February 2009)


Component Architectures

Service Registry Plugin

Swordfish supports the connection to different service registries in order to allow dynamic endpoint resolution. This flexibility is realized through the service registry plugin.

Policy Trading Plugin

Swordfish shall support flexible support for policy trading at service resolution. This includes selection of a suitable service provider based on a consumer policy and trading of an agreed policy for service invocation. Here the team provides sketches of the component architecture of an exemplary implementation Policy Trading Plugin.

Internal Service Proxy Plugin

Internal Service Proxy.

Interceptor Framework

The Interceptor Framework provides generic support for intercepting messages in different stages of the communication between consumer and provider. It enables implementations that allow the distinguishing role (consumer / provider) and scope (request, response).

Technical Parameter Propagation

Technical Parameter Propagation.

Further Reading

For further details also have a look at: Swordfish Papers, Articles and Presentations



Swordfish Wiki Home

Back to the top