-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: CSD2
-
Fix Version/s: CSD2
-
Component/s: Spec
-
Labels:None
-
Proposal:
The current <Interfaces> element requires a reshape and extensions. A reshape is required to achieve
consistency with the usual practice that "coherent entities" have a single interface only, (ii) to allow implementation artifacts not only for operations, and (iii) to rename some language elements to comply with common terminology. Extensions are required to better support REST APIs as interface implementations. The current <Interfaces> element requires a reshape and extensions. A reshape is required to achieve consistency with the usual practice that "coherent entities" have a single interface only, (ii) to allow implementation artifacts not only for operations, and (iii) to rename some language elements to comply with common terminology. Extensions are required to better support REST APIs as interface implementations. -
Resolution:
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.