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 294764

Revision as of 12:04, 17 November 2009 by Josh.hester.sas.com (Talk | contribs) (Design details)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Code to dynamically load localization translation string file

This is the design document for bugzilla 294764.

Change History

Name: Date: Revised Sections:
Josh Hester November 10, 2009
  • Initial version

Workload Estimation

Rough workload estimate in person weeks
Process Sizing Names of people doing the work
Design 1 Josh Hester
Code 1 Josh Hester
Test 1 Josh Hester
Documentation 0
Build and infrastructure 0
Code review, etc.* 1
TOTAL 1

'* - includes other committer work (e.g. check-in, contribution tracking)

Purpose

This enhancement will convert our tooling work from using the hand written SPI to parse SDDs and SPDs to classes generated by JAXB from our schema.

Requirements

  • BTG must work essentially as before, with changes being under the covers.


Design details

  • SPI and JAXB use very similar methods with the method names for the getters and setters changing only slightly and not always. The code changes will reflect these different method names while the overall logic and structure of the code will not change.

For instance in the DeploymentDescriptorType in SPI contains Resources:

dd.setResources(

while jaxb follows the schema more closely so that deployment descriptor contains topology which contains resources:

dd.getTopologygetResource().add(newItem)

Impacts of this enhancement

  • We will be able to more easily accomodate schema changes.
  • Our tptp tests which also use SPI will need to change.

Open Issues/Questions

Copyright © Eclipse Foundation, Inc. All Rights Reserved.