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

COSMOS Design 220949: vanilla web services

Change History

Name: Date: Revised Sections:
Hubert Leung 03/04/2008
  • Initial version

Workload Estimation

Rough workload estimate in person weeks
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:

  1. Java 5
  2. Axis2 without JAX-WS
  3. JAX-B

Option 2:

  1. Java5
  2. AXIS2 1.4
    • JAX-WS 2.1 runtime
    • JAX-B 2.1
  3. 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 class, and operations are mapped to Java methods.

Open Issues/Questions

All reviewer feedback should go in the Talk page for 220949.

Back to the top