[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (TOSCA-4) Modification of the <Interfaces> element of Node Types
[ http://tools.oasis-open.org/issues/browse/TOSCA-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29379#action_29379 ]
Frank Leymann commented on TOSCA-4:
------------------------------------
Addressing Steve's Comment from 07/Feb/12:
RESTful operations can pass input in the "name=value" format: this is referred to as "query string". The Parameter elements describe exactly the "name" part of a query string.
Note, that we do not foresee that the query string can pass matrix parameters (i.e. those in the "name_1;name_2=value,name_3=value...") because this is not supported by all http servers.
Form-based passing of input and output is covered by specifying corresponding QNames of the requestBody and/or responseBody attributes.
The implementation artifact has a type, and the content of such an implementation artifact is type-specific. We may define a couple of types (and their formats). One of these types may define that the location of the script is the content of the artifact, while another type of artifact might define how to specify scripts in place. And of course each of these types may define as content any kind and any number of type-specific "metadata" for the implementation artifact.
> Modification of the <Interfaces> element of Node Types
> ------------------------------------------------------
>
> Key: TOSCA-4
> URL: http://tools.oasis-open.org/issues/browse/TOSCA-4
> Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
> Issue Type: Bug
> Components: Spec
> Affects Versions: WD1
> Reporter: Frank Leymann
> Assignee: Frank Leymann
> Priority: Critical
> Fix For: WD1
>
>
> We propose to drop the <Interfaces> element of node types and support (at most) a single <Interface> for a <NodeType> element. This interface will consist of one of more operations. The implication is that the current <Operation> element must be renamed to better reflect its purpose; because its purpose is to define scripts as operations of node types, we propose to rename todays <Operation> into <ScriptOperation>. As a result of the renaming, an <Interface> consists of <Operation>s that may be either an operation of a port type (i.e. a WSDL operation), a REST API, or a script operation.
> The current <REST> element does not suffice to support the variety of REST APIs found in the industry. The proposal is to extend the current definition accordingly. Beside allowing to define the HTTP method to be used, both, abs_path and absolte_URI variants of request URIs must be supported. The optional body of the request message and the response message must be specifiable. Next, a pure URI variant of passing parameters must be supported, i.e. the new syntax must support to define a URI query string. Also, key HTTP header fields that are relevant for the request must be specifiable.
> Finally, not only script-based operations require implementation artifacts. For example, a REST API may be represented by a WAR file implementing the REST API. This implies to factor out the corresponding <ImplementationArtifacts> element into the embracing (new) <Operation> element.
--
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]