[OASIS Issue Tracker] (TOSCA-228) Discuss "Final" concept for Types, Operation and properties

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

Matthew Rutkowski  created TOSCA-228:
----------------------------------------

             Summary: Discuss "Final" concept for Types, Operation and properties
                 Key: TOSCA-228
                 URL: https://issues.oasis-open.org/browse/TOSCA-228
             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
          Issue Type: New Feature
          Components: Profile-YAML
    Affects Versions: CSD03
            Reporter: Matthew Rutkowski 
             Fix For: CSD04


Currently in TOSCA, anyone who subclasses a Type (Node, Relationship, Data, Interface, etc.)  is able to override the settings, behaviors (interfaces), operations (implementation artifacts), property defaults (values), etc.  In all cases "override" is the default allowed behavoir.  This is even allowed, in some cases for Templates that are based on Types.

In other words, there is no way for a Type designers to "lock in" or finalize their implementations, tested values, or behaviors.

In other languages the concept of finalization at the Type/class, Operations/method and property/variable levels is considered (typically through some keyword like "final").  In order for TOSCA Type system to be "future proof" and allow "experts" to "lock in" their carefully designed types, we need to consider such an option.



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