AW: [tosca] [OASIS Issue Tracker] Commented: (TOSCA-76) Re-Introduce the "Entry-Service-Template" Field in CSAR

I don't want to defer the spec. If there is no other way to fix the bug for V1, we'll move it to v.next

Gruss/Regards, 
Frank

 
OASIS Issues Tracker <> hat geschrieben:

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

Paul Lipton  commented on TOSCA-76:
-----------------------------------

Are you proposing this as a fix for the current spec in public review (this will require a second 15 day review, as discussed in the TC last week) or as a proposed fix to v.next? 

> Re-Introduce the "Entry-Service-Template" Field in CSAR
> -------------------------------------------------------
>
>                 Key: TOSCA-76
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-76
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Bug
>          Components: Spec
>    Affects Versions: CSD03
>            Reporter: Frank Leymann 
>
> Until WD-12 the Block_0 of a CSAR contained the Entry-Service-Template field.  WD-13 removed this field, basically because the newly introduced <Definition> files do not necessarily contain a <ServiceTemplate> element at all to support modular definition and reuse of other TOSCA entities. Thus, the Entry-Service-Template field does not make any sense for a CSAR that does not package a <ServiceTemplate> element at all.

-- 
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: 
For additional commands, e-mail: