[OASIS Issue Tracker] (SRAMP-65) Target enum improvements

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Brett Meyer created SRAMP-65:
--------------------------------

             Summary: Target enum improvements
                 Key: SRAMP-65
                 URL: https://issues.oasis-open.org/browse/SRAMP-65
             Project: OASIS SOA Repository Artifact Model and Protocol (S-RAMP) TC
          Issue Type: Improvement
    Affects Versions: 1.0
            Reporter: Brett Meyer


Currently, each Target sub-class carries its own instance of an artifactType enum.  Those enums all represent subsections of BaseArtifactEnum, providing only the values applicable to that targeted artifact type.

While I understand the intent behind that setup, it tends to muck up the actual implementation.  Can we think of alternatives that would allow target type restrictions, but also use one single enum?

Off the top of my head, I'm not sure what that would look like...



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)