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.
Difference between revisions of "Corona Design SOA"
| Line 4: | Line 4: | ||
[[Image:CoronaSOAArchitecture.png]] | [[Image:CoronaSOAArchitecture.png]] | ||
| + | |||
| + | '''HTTP Service Provider BUNDLE''' | ||
| + | |||
| + | '''Isolation Layer Implementation BUNDLE - SOAP Service Provider''' | ||
| + | |||
| + | '''OSGi/Muse BUNDLE''' | ||
| + | |||
| + | '''Resource BUNDLES''' | ||
Revision as of 14:58, 24 May 2006
The Corona SOA core will be based on an integration of the Apache Muse Project, which is currently provisioning for a new release. At the heart of the new Muse release is the idea of isolating the implementation details of WSDM-managed resources from specific deployment containers. This is accomplished by the creation of an abstraction layer that sits between the Muse core and the SOAP provider that hosts it.
The initial provisioning of Muse lacks an OSGi-oriented implementation of these abstraction layers. We (Corona) propose to provide this implementation as part of Apache/Muse, and to add on to it to support Corona-specific extensions.
HTTP Service Provider BUNDLE
Isolation Layer Implementation BUNDLE - SOAP Service Provider
OSGi/Muse BUNDLE
Resource BUNDLES