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 220949
Contents
Change History
Name: | Date: | Revised Sections: |
---|---|---|
Hubert Leung | 03/04/2008 |
|
Workload Estimation
Process | Sizing | Names of people doing the work |
---|---|---|
Design | 0.4 | Hubert Leung |
Code | 1.4 | Hubert Leung |
Test | 0.6 | Hubert Leung |
Documentation | 0.2 | Hubert Leung |
Build and infrastructure | 0.4 | Saurabh Dravid |
Code review, etc.* | ||
TOTAL | 3 |
'* - includes other committer work (e.g. check-in, contribution tracking)
Purpose
The current implementation of the data manager framework makes use of the COSMOS annotations and MUSE. The SOAP message does not follow the document/literal style because there are wrapping elements around the message payload. We are also using WS-Addressing in the message header. In order to ensure interoperability of the MDRs with non-COSMOS MDRs and to comply with the CMDBf standard more strictly, we want to support stateless web services in COSMOS. SOAP messages will not require WS-Addressing and use document/literal payload style.
Design
Technology Stack
[NOT FINALIZED]
Option 1:
- Java 5
- Axis2 without JAX-WS
- JAX-B
Option 2:
- Java5
- AXIS2 1.4
- JAX-WS 2.1 runtime
- JAX-B 2.1
- Use JAX-WS tooling from Java6
Programming model
Web service and client code can be generated from WSDL files provided by the CMDBf standard. Port type is mapped to a Java interface, and operations are mapped to Java methods.
The class hierachy of the current programming model should remain the same.
Impacts
- Since the SOAP message payload format will change, UI will need to adapt to the change when parsing SOAP body for data.
- Affects the way broker and management domain store addresses and properties of data managers.
Open Issues/Questions
All reviewer feedback should go in the Talk page for 220949.