Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Swordfish Documentation: Architecture"
| Line 9: | Line 9: | ||
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 == | == Component Architecture for the Policy Trading Plugin == | ||
| Line 20: | Line 19: | ||
== Design Options for Interceptor Framework == | == Design Options for Interceptor Framework == | ||
[[Swordfish_Documentation:_Architecture:_Interceptor_Framework | Interceptor Framework]]. | [[Swordfish_Documentation:_Architecture:_Interceptor_Framework | Interceptor Framework]]. | ||
| + | |||
| + | == Component Architecture for the Technical Parameter Propagation == | ||
| + | [[Swordfish_Documentation:_Architecture:_Parameter_Propagation | Technical Parameter Propagation]]. | ||
== Further Reading == | == Further Reading == | ||
Revision as of 04:19, 16 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)
Contents
- 1 Component Architecture for the Service Registry Plugin
- 2 Component Architecture for the Policy Trading Plugin
- 3 Component Architecture for the Internal Service Proxy Plugin
- 4 Design Options for Interceptor Framework
- 5 Component Architecture for the Technical Parameter Propagation
- 6 Further Reading
Component Architecture for the 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.
Component Architecture for the 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.
Component Architecture for the Internal Service Proxy Plugin
Design Options for Interceptor Framework
Component Architecture for the Technical Parameter Propagation
Technical Parameter Propagation.
Further Reading
For further details also have a look at: Swordfish Papers, Articles and Presentations