Bug 1001435

Summary: Move content spec constants (like "Title") to common library
Product: [Community] PressGang CCMS Reporter: Matthew Casperson <mcaspers>
Component: CSProcessorAssignee: Lee Newson <lnewson>
Status: CLOSED CURRENTRELEASE QA Contact: Matthew Casperson <mcaspers>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.1CC: cbredesen, lnewson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-09 05:17:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Matthew Casperson 2013-08-27 04:20:34 UTC
Using the content spec REST entities often involves looking up specific metadata nodes. It would be nice if the constant metadata nodes had names in a common library like RESTv1Constants so we could write code like

String title = "";
for (final RESTCSNodeCollectionItemV1 csNode : spec.getItem().getChildren_OTM().getItems()) {
    if (csNode.getItem().getNodeType() == RESTCSNodeTypeV1.META_DATA &&
            csNode.getItem().getTitle().equals(RESTv1Constants.CONTENT_SPEC_METADATA_TITLE)) {
        title = csNode.getItem().getAdditionalText();
        break;
    }
}

Comment 3 Lee Newson 2013-08-28 02:37:13 UTC
Moved the MetaData constants to the CommonConstants class. See https://github.com/pressgang-ccms/PressGangCCMSCommonUtilities/commit/f0895164aae9dac22b86cd8582d3aa33a23be33c