OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (TOSCA-55) issue of ImplementationArtifact without operationName definition


    [ http://tools.oasis-open.org/issues/browse/TOSCA-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31287#action_31287 ] 

Paul Lipton  commented on TOSCA-55:
-----------------------------------

Due to standing rules, this will be tentatively scheduled for the meeting of October 4th unless resolved to the reporter's satisfaction by comment prior to that date. 

> issue of ImplementationArtifact without operationName definition
> ----------------------------------------------------------------
>
>                 Key: TOSCA-55
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-55
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>    Affects Versions: CSD05
>            Reporter: Paul Zhang
>
> The ImplementationArtifact element has an OPTIONAL attribute called operationName. According to the specification (Line 968), if this attribute is not specified, the implementation artifact is assumed to provide the implementation for all operations defined within the containing interface. Here is a scenario that current overriding rules can not cover. 
> Consider a Node Type "A1" defining two operations within one interface. The Node Type "A1" also defines an implementation artifact "X" in the interface with no operation name specified (for example, the implementation artifact "X" is a war and operations are REST operations). This means both operations take "X" as their implementation artifacts. Developers define the Node Type "B" derived from Node Type "A1" and they want to use a new implementation artifact "Y" for both operations to substitute the implementation artifact "X". According to the current overriding rules, if an implementation artifact defined by the Node Type under definition has the same operation name and type as an implementation artifact of the Node Type derived from, the former implementation artifact substitutes the latter one. In this case, the implementation artifact "X" cannot be substituted because it has no operation name specified. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]