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.
COSMOS Design 209980
Contents
MDR (and Data Manager) deployment outside of OSGi environment
Change History
| Name: | Date: | Revised Sections: |
|---|---|---|
| John Todd | 01/22/2008 |
|
Workload Estimation
| Process | Sizing | Names of people doing the work |
|---|---|---|
| Design | 1PW | Hubert |
| Code | 3PW | Hubert |
| Test | unknown | TBA |
| Documentation | unknown | TBA |
| Build and infrastructure | unknown | TBA |
| Code review, etc.* | unknown | TBA |
| TOTAL | unknown | TBA |
'* - includes other committer work (e.g. check-in, contribution tracking)
Terminologies/Acronyms
The terminologies/acronyms below are commonly used throughout this document. The list below defines each term regarding how it is used in this document:
| Term | Definition |
|---|---|
| MDR | Management Data Repository |
Purpose
- Port the data manager and MDR Framework to allow data managers and MDRs to be deployed on a web server (Tomcat).
- Support non-MUWS clients.
Requirements
- annotation implementation in ME that supports J2EE - Axis2 JAX-WS implementation
Implementation details
Requirement: Update the framework to allow data managers be deployed on Tomcat.
- Port the current implementation to use the annotation in ME subproject, and change some of the framework design (such as application configuration) to support both OSGi and web environment.
- A requirement is to make MDRs be interoperable with web service clients that don't support MUWS. Provide an alternativie set of APIs that support JAX-WS.
Test Coverage
list test cases here.
Open Issues
This task is still being scoped.