Commit dc24f4f0 authored by Spiros Koulouzis's avatar Spiros Koulouzis

throw exception if cloud name is null

parent 0f38c7e5
......@@ -72,7 +72,7 @@
<h1 class="page-header">Files and Libraries</h1>
<h3 id="artifact_gwt_json_overlay">GWT JSON Overlay</h3>
<p class="lead">Created October 19, 2017</p>
<p class="lead">Created October 27, 2017</p>
<p> <p>
The <a href="http://code.google.com/webtoolkit/">Google Web Toolkit</a> JSON Overlay library provides the JSON Overlays that
can be used to access the Web service API for this application.
......@@ -97,7 +97,7 @@
</tbody>
</table>
<h3 id="artifact_java_json_client_library">Java JSON Client Library</h3>
<p class="lead">Created October 19, 2017</p>
<p class="lead">Created October 27, 2017</p>
<p><p>
The Java client-side library is used to provide the set of Java objects that can be serialized
to/from JSON using <a href="http://jackson.codehaus.org/">Jackson</a>. This is useful for accessing the
......@@ -127,7 +127,7 @@
</tbody>
</table>
<h3 id="artifact_java_xml_client_library">Java XML Client Library</h3>
<p class="lead">Created October 19, 2017</p>
<p class="lead">Created October 27, 2017</p>
<p><p>
The Java client-side library is used to access the Web service API for this application using Java.
</p>
......@@ -144,18 +144,18 @@
<tbody data-link="row" class="rowlink">
<tr class="clickable-row" data-href="drip-api-xml-client.jar">
<td><span class="downloadfile-name">drip-api-xml-client.jar</span></td>
<td><span class="downloadfile-size">24.64K</span></td>
<td><span class="downloadfile-size">24.67K</span></td>
<td><span class="downloadfile-description">The binaries for the Java XML client library.</span></td>
</tr>
<tr class="clickable-row" data-href="drip-api-xml-client-xml-sources.jar">
<td><span class="downloadfile-name">drip-api-xml-client-xml-sources.jar</span></td>
<td><span class="downloadfile-size">22.35K</span></td>
<td><span class="downloadfile-size">22.38K</span></td>
<td><span class="downloadfile-description">The sources for the Java XML client library.</span></td>
</tr>
</tbody>
</table>
<h3 id="artifact_js_client_library">JavaScript Client Library</h3>
<p class="lead">Created October 19, 2017</p>
<p class="lead">Created October 27, 2017</p>
<p><p>
The JavaScript client-side library defines classes that can be (de)serialized to/from JSON.
This is useful for accessing the resources that are published by this application, but only
......@@ -184,13 +184,13 @@
<tbody data-link="row" class="rowlink">
<tr class="clickable-row" data-href="drip-api-js.zip">
<td><span class="downloadfile-name">drip-api-js.zip</span></td>
<td><span class="downloadfile-size">5.44K</span></td>
<td><span class="downloadfile-size">5.45K</span></td>
<td><span class="downloadfile-description">&nbsp;</span></td>
</tr>
</tbody>
</table>
<h3 id="artifact_php_json_client_library">PHP JSON Client Library</h3>
<p class="lead">Created October 19, 2017</p>
<p class="lead">Created October 27, 2017</p>
<p><p>
The PHP JSON client-side library defines the PHP classes that can be (de)serialized to/from JSON.
This is useful for accessing the resources that are published by this application, but only
......@@ -213,13 +213,13 @@
<tbody data-link="row" class="rowlink">
<tr class="clickable-row" data-href="drip-api-php.zip">
<td><span class="downloadfile-name">drip-api-php.zip</span></td>
<td><span class="downloadfile-size">6.01K</span></td>
<td><span class="downloadfile-size">6.05K</span></td>
<td><span class="downloadfile-description">&nbsp;</span></td>
</tr>
</tbody>
</table>
<h3 id="artifact_php_xml_client_library">PHP XML Client Library</h3>
<p class="lead">Created October 19, 2017</p>
<p class="lead">Created October 27, 2017</p>
<p><p>
The PHP client-side library defines the PHP classes that can be (de)serialized to/from XML.
This is useful for accessing the resources that are published by this application, but only
......@@ -251,7 +251,7 @@
</tbody>
</table>
<h3 id="artifact_ruby_json_client_library">Ruby JSON Client Library</h3>
<p class="lead">Created October 19, 2017</p>
<p class="lead">Created October 27, 2017</p>
<p><p>
The Ruby JSON client-side library defines the Ruby classes that can be (de)serialized to/from JSON.
This is useful for accessing the REST endpoints that are published by this application, but only
......
This diff is collapsed.
......@@ -144,7 +144,8 @@ used as a archive / log of ansible executions</p>
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -157,7 +158,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -81,7 +81,7 @@ class</p>
</thead>
<tbody>
<tr>
<td> <span class="property-name">host</span>
<td> <span class="property-name">cloudDeploymentDomain</span>
</td>
<td> <span class="datatype-reference">string
</span>
......@@ -90,7 +90,7 @@ class</p>
</td>
</tr>
<tr>
<td> <span class="property-name">cloudDeploymentDomain</span>
<td> <span class="property-name">vmType</span>
</td>
<td> <span class="datatype-reference">string
</span>
......@@ -99,7 +99,7 @@ class</p>
</td>
</tr>
<tr>
<td> <span class="property-name">delta</span>
<td> <span class="property-name">end</span>
</td>
<td> <span class="datatype-reference">number
</span>
......@@ -108,18 +108,18 @@ class</p>
</td>
</tr>
<tr>
<td> <span class="property-name">vmType</span>
<td> <span class="property-name">delta</span>
</td>
<td> <span class="datatype-reference">string
<td> <span class="datatype-reference">number
</span>
</td>
<td> <span class="property-description"></span>
</td>
</tr>
<tr>
<td> <span class="property-name">end</span>
<td> <span class="property-name">host</span>
</td>
<td> <span class="datatype-reference">number
<td> <span class="datatype-reference">string
</span>
</td>
<td> <span class="property-description"></span>
......@@ -144,7 +144,8 @@ class</p>
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -157,7 +158,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......@@ -165,11 +167,11 @@ object is saved.</span></td>
<p class="lead">Example</p>
<pre class="prettyprint language-js example">{
&quot;host&quot; : &quot;147.228.242.58&quot;,
&quot;cloudDeploymentDomain&quot; : &quot;us-east-1&quot;,
&quot;delta&quot; : 12345,
&quot;vmType&quot; : &quot;...&quot;,
&quot;end&quot; : 12345,
&quot;delta&quot; : 12345,
&quot;host&quot; : &quot;147.228.242.58&quot;,
&quot;start&quot; : 12345,
&quot;owner&quot; : &quot;user1&quot;,
&quot;id&quot; : &quot;58e3946e0fb4f562d84ba1ad&quot;,
......
......@@ -126,7 +126,8 @@ to request for resources.</p>
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -139,7 +140,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -121,7 +121,8 @@ chosen deployment manager (for now only ansible)
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -134,7 +135,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -152,7 +152,8 @@ chosen deployment manager (for now only ansible)
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -165,7 +166,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -117,7 +117,8 @@ logging in VMs.</p>
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -130,7 +131,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -101,7 +101,8 @@ abstract types such as TOSCA.</p>
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -114,7 +115,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -144,7 +144,8 @@ class</p>
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -157,7 +158,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -69,7 +69,7 @@ class</p>
<dl class="dl-horizontal">
<dt>Subtypes</dt>
<dd><a href="json_KeyPair.html">KeyPair</a>, <a href="json_ScaleRequest.html">ScaleRequest</a>, <a href="json_AnsibleOutput.html">AnsibleOutput</a>, <a href="json_CloudCredentials.html">CloudCredentials</a>, <a href="json_BenchmarkResult.html">BenchmarkResult</a>, <a href="json_DeployResponse.html">DeployResponse</a>, <a href="json_ProvisionRequest.html">ProvisionRequest</a>, <a href="json_Script.html">Script</a>, <a href="json_KeyValueHolder.html">KeyValueHolder</a>, <a href="json_DeployRequest.html">DeployRequest</a>, <a href="json_MonitorringMessage.html">MonitorringMessage</a>, <a href="json_ProvisionResponse.html">ProvisionResponse</a></dd>
<dd><a href="json_KeyPair.html">KeyPair</a>, <a href="json_ScaleRequest.html">ScaleRequest</a>, <a href="json_AnsibleOutput.html">AnsibleOutput</a>, <a href="json_CloudCredentials.html">CloudCredentials</a>, <a href="json_BenchmarkResult.html">BenchmarkResult</a>, <a href="json_DeployResponse.html">DeployResponse</a>, <a href="json_ProvisionRequest.html">ProvisionRequest</a>, <a href="json_Script.html">Script</a>, <a href="json_KeyValueHolder.html">KeyValueHolder</a>, <a href="json_DeployRequest.html">DeployRequest</a>, <a href="json_ProvisionResponse.html">ProvisionResponse</a>, <a href="json_MonitorringMessage.html">MonitorringMessage</a></dd>
</dl>
<table class="table datatype-properties">
......@@ -89,7 +89,8 @@ class</p>
</span>
</td>
<td> <span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span>
</td>
</tr>
<tr>
......@@ -108,7 +109,8 @@ object is saved.</span>
<td> <span class="datatype-reference">number
</span>
</td>
<td> <span class="property-description">The object's creation date in unix time stamp</span>
<td> <span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span>
</td>
</tr>
</tbody>
......
......@@ -139,7 +139,8 @@ provisioner to request for cloud resources.</p>
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -152,7 +153,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -147,7 +147,8 @@
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -160,7 +161,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -120,7 +120,8 @@ request 1 we'll have 1</span>
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -133,7 +134,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -107,7 +107,8 @@
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -120,7 +121,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -534,7 +534,8 @@ class]]>
<xs:annotation>
<xs:documentation>
<![CDATA[The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call]]>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST]]>
</xs:documentation>
</xs:annotation>
</xs:element>
......@@ -791,18 +792,18 @@ class]]>
<xs:complexContent>
<xs:extension base="ownedObject">
<xs:sequence>
<xs:element name="host" type="xs:string" minOccurs="0">
</xs:element>
<xs:element name="vmType" type="xs:string" minOccurs="0">
</xs:element>
<xs:element name="cloudDeploymentDomain" type="xs:string" minOccurs="0">
</xs:element>
<xs:element name="delta" type="xs:dateTime" minOccurs="0">
</xs:element>
<xs:element name="host" type="xs:string" minOccurs="0">
</xs:element>
<xs:element name="end" type="xs:dateTime" minOccurs="0">
</xs:element>
<xs:element name="start" type="xs:dateTime" minOccurs="0">
</xs:element>
<xs:element name="delta" type="xs:dateTime" minOccurs="0">
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
......
......@@ -144,11 +144,11 @@ Content-Type: application/json
<code class="prettyprint language-js">
[ {
&quot;host&quot; : &quot;147.228.242.58&quot;,
&quot;cloudDeploymentDomain&quot; : &quot;us-east-1&quot;,
&quot;delta&quot; : 12345,
&quot;vmType&quot; : &quot;...&quot;,
&quot;end&quot; : 12345,
&quot;delta&quot; : 12345,
&quot;host&quot; : &quot;147.228.242.58&quot;,
&quot;start&quot; : 12345,
&quot;owner&quot; : &quot;user1&quot;,
&quot;id&quot; : &quot;58e3946e0fb4f562d84ba1ad&quot;,
......@@ -514,11 +514,11 @@ Content-Type: application/json
<code class="prettyprint language-js">
{
&quot;host&quot; : &quot;147.228.242.58&quot;,
&quot;cloudDeploymentDomain&quot; : &quot;us-east-1&quot;,
&quot;delta&quot; : 12345,
&quot;vmType&quot; : &quot;...&quot;,
&quot;end&quot; : 12345,
&quot;delta&quot; : 12345,
&quot;host&quot; : &quot;147.228.242.58&quot;,
&quot;start&quot; : 12345,
&quot;owner&quot; : &quot;user1&quot;,
&quot;id&quot; : &quot;58e3946e0fb4f562d84ba1ad&quot;,
......
......@@ -193,7 +193,8 @@ used as a archive / log of ansible executions</p>
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -211,7 +211,8 @@ class</p>
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......@@ -219,12 +220,12 @@ the DAO saves the object based on the principal how made the call</span></td>
<p class="lead">Example</p>
<pre class="prettyprint language-xml example">&lt;b-----&gt;
&lt;host&gt;147.228.242.58&lt;/host&gt;
&lt;vmType&gt;...&lt;/vmType&gt;
&lt;cloudDeploymentDomain&gt;us-east-1&lt;/cloudDeploymentDomain&gt;
&lt;delta&gt;...&lt;/delta&gt;
&lt;host&gt;147.228.242.58&lt;/host&gt;
&lt;end&gt;...&lt;/end&gt;
&lt;start&gt;...&lt;/start&gt;
&lt;delta&gt;...&lt;/delta&gt;
&lt;owner&gt;user1&lt;/owner&gt;
&lt;/b-----&gt;
</pre>
......
......@@ -175,7 +175,8 @@ to request for resources.</p>
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -161,7 +161,8 @@ chosen deployment manager (for now only ansible)
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -201,7 +201,8 @@ chosen deployment manager (for now only ansible)
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -157,7 +157,8 @@ logging in VMs.</p>
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -105,7 +105,8 @@ abstract types such as TOSCA.</p>
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -211,7 +211,8 @@ class</p>
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -105,7 +105,8 @@ class</p>
</span>
</td>
<td> <span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span>
</td>
</tr>
</tbody>
......
......@@ -177,7 +177,8 @@ provisioner to request for cloud resources.</p>
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -191,7 +191,8 @@
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -160,7 +160,8 @@ deployment scale only swarm deployments are supported.</span>
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -138,7 +138,8 @@
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -72,7 +72,7 @@
<h1 class="page-header">Files and Libraries</h1>
<h3 id="artifact_gwt_json_overlay">GWT JSON Overlay</h3>
<p class="lead">Created October 19, 2017</p>
<p class="lead">Created October 27, 2017</p>
<p> <p>
The <a href="http://code.google.com/webtoolkit/">Google Web Toolkit</a> JSON Overlay library provides the JSON Overlays that
can be used to access the Web service API for this application.
......@@ -97,7 +97,7 @@
</tbody>
</table>
<h3 id="artifact_java_json_client_library">Java JSON Client Library</h3>
<p class="lead">Created October 19, 2017</p>
<p class="lead">Created October 27, 2017</p>
<p><p>
The Java client-side library is used to provide the set of Java objects that can be serialized
to/from JSON using <a href="http://jackson.codehaus.org/">Jackson</a>. This is useful for accessing the
......@@ -127,7 +127,7 @@
</tbody>
</table>
<h3 id="artifact_java_xml_client_library">Java XML Client Library</h3>
<p class="lead">Created October 19, 2017</p>
<p class="lead">Created October 27, 2017</p>
<p><p>
The Java client-side library is used to access the Web service API for this application using Java.
</p>
......@@ -144,18 +144,18 @@
<tbody data-link="row" class="rowlink">
<tr class="clickable-row" data-href="drip-api-xml-client.jar">
<td><span class="downloadfile-name">drip-api-xml-client.jar</span></td>
<td><span class="downloadfile-size">24.64K</span></td>
<td><span class="downloadfile-size">24.67K</span></td>
<td><span class="downloadfile-description">The binaries for the Java XML client library.</span></td>
</tr>
<tr class="clickable-row" data-href="drip-api-xml-client-xml-sources.jar">
<td><span class="downloadfile-name">drip-api-xml-client-xml-sources.jar</span></td>
<td><span class="downloadfile-size">22.35K</span></td>
<td><span class="downloadfile-size">22.38K</span></td>
<td><span class="downloadfile-description">The sources for the Java XML client library.</span></td>
</tr>
</tbody>
</table>
<h3 id="artifact_js_client_library">JavaScript Client Library</h3>
<p class="lead">Created October 19, 2017</p>
<p class="lead">Created October 27, 2017</p>
<p><p>
The JavaScript client-side library defines classes that can be (de)serialized to/from JSON.
This is useful for accessing the resources that are published by this application, but only
......@@ -184,13 +184,13 @@
<tbody data-link="row" class="rowlink">
<tr class="clickable-row" data-href="drip-api-js.zip">
<td><span class="downloadfile-name">drip-api-js.zip</span></td>
<td><span class="downloadfile-size">5.44K</span></td>
<td><span class="downloadfile-size">5.45K</span></td>
<td><span class="downloadfile-description">&nbsp;</span></td>
</tr>
</tbody>
</table>
<h3 id="artifact_php_json_client_library">PHP JSON Client Library</h3>
<p class="lead">Created October 19, 2017</p>
<p class="lead">Created October 27, 2017</p>
<p><p>
The PHP JSON client-side library defines the PHP classes that can be (de)serialized to/from JSON.
This is useful for accessing the resources that are published by this application, but only
......@@ -213,13 +213,13 @@
<tbody data-link="row" class="rowlink">
<tr class="clickable-row" data-href="drip-api-php.zip">
<td><span class="downloadfile-name">drip-api-php.zip</span></td>
<td><span class="downloadfile-size">6.01K</span></td>
<td><span class="downloadfile-size">6.05K</span></td>
<td><span class="downloadfile-description">&nbsp;</span></td>
</tr>
</tbody>
</table>
<h3 id="artifact_php_xml_client_library">PHP XML Client Library</h3>
<p class="lead">Created October 19, 2017</p>
<p class="lead">Created October 27, 2017</p>
<p><p>
The PHP client-side library defines the PHP classes that can be (de)serialized to/from XML.
This is useful for accessing the resources that are published by this application, but only
......@@ -251,7 +251,7 @@
</tbody>
</table>
<h3 id="artifact_ruby_json_client_library">Ruby JSON Client Library</h3>
<p class="lead">Created October 19, 2017</p>
<p class="lead">Created October 27, 2017</p>
<p><p>
The Ruby JSON client-side library defines the Ruby classes that can be (de)serialized to/from JSON.
This is useful for accessing the REST endpoints that are published by this application, but only
......
This diff is collapsed.
......@@ -144,7 +144,8 @@ used as a archive / log of ansible executions</p>
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -157,7 +158,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -81,7 +81,7 @@ class</p>
</thead>
<tbody>
<tr>
<td> <span class="property-name">cloudDeploymentDomain</span>
<td> <span class="property-name">vmType</span>
</td>
<td> <span class="datatype-reference">string
</span>
......@@ -90,16 +90,16 @@ class</p>
</td>
</tr>
<tr>
<td> <span class="property-name">vmType</span>
<td> <span class="property-name">start</span>
</td>
<td> <span class="datatype-reference">string
<td> <span class="datatype-reference">number
</span>
</td>
<td> <span class="property-description"></span>
</td>
</tr>
<tr>
<td> <span class="property-name">start</span>
<td> <span class="property-name">delta</span>
</td>
<td> <span class="datatype-reference">number
</span>
......@@ -108,16 +108,16 @@ class</p>
</td>
</tr>
<tr>
<td> <span class="property-name">end</span>
<td> <span class="property-name">host</span>
</td>
<td> <span class="datatype-reference">number
<td> <span class="datatype-reference">string
</span>
</td>
<td> <span class="property-description"></span>
</td>
</tr>
<tr>
<td> <span class="property-name">delta</span>
<td> <span class="property-name">end</span>
</td>
<td> <span class="datatype-reference">number
</span>
......@@ -126,7 +126,7 @@ class</p>
</td>
</tr>
<tr>
<td> <span class="property-name">host</span>
<td> <span class="property-name">cloudDeploymentDomain</span>
</td>
<td> <span class="datatype-reference">string
</span>
......@@ -144,7 +144,8 @@ class</p>
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -157,7 +158,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......@@ -165,12 +167,12 @@ object is saved.</span></td>
<p class="lead">Example</p>
<pre class="prettyprint language-js example">{
&quot;cloudDeploymentDomain&quot; : &quot;us-east-1&quot;,
&quot;vmType&quot; : &quot;...&quot;,
&quot;start&quot; : 12345,
&quot;end&quot; : 12345,
&quot;delta&quot; : 12345,
&quot;host&quot; : &quot;147.228.242.58&quot;,
&quot;end&quot; : 12345,
&quot;cloudDeploymentDomain&quot; : &quot;us-east-1&quot;,
&quot;owner&quot; : &quot;user1&quot;,
&quot;id&quot; : &quot;58e3946e0fb4f562d84ba1ad&quot;,
&quot;timestamp&quot; : 1499793079011
......
......@@ -126,7 +126,8 @@ to request for resources.</p>
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -139,7 +140,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -121,7 +121,8 @@ chosen deployment manager (for now only ansible)
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -134,7 +135,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -152,7 +152,8 @@ chosen deployment manager (for now only ansible)
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -165,7 +166,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -117,7 +117,8 @@ logging in VMs.</p>
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -130,7 +131,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -101,7 +101,8 @@ abstract types such as TOSCA.</p>
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -114,7 +115,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -144,7 +144,8 @@ class</p>
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -157,7 +158,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -69,7 +69,7 @@ class</p>
<dl class="dl-horizontal">
<dt>Subtypes</dt>
<dd><a href="json_KeyPair.html">KeyPair</a>, <a href="json_ScaleRequest.html">ScaleRequest</a>, <a href="json_AnsibleOutput.html">AnsibleOutput</a>, <a href="json_CloudCredentials.html">CloudCredentials</a>, <a href="json_BenchmarkResult.html">BenchmarkResult</a>, <a href="json_DeployResponse.html">DeployResponse</a>, <a href="json_ProvisionRequest.html">ProvisionRequest</a>, <a href="json_Script.html">Script</a>, <a href="json_KeyValueHolder.html">KeyValueHolder</a>, <a href="json_DeployRequest.html">DeployRequest</a>, <a href="json_MonitorringMessage.html">MonitorringMessage</a>, <a href="json_ProvisionResponse.html">ProvisionResponse</a></dd>
<dd><a href="json_KeyPair.html">KeyPair</a>, <a href="json_AnsibleOutput.html">AnsibleOutput</a>, <a href="json_ScaleRequest.html">ScaleRequest</a>, <a href="json_CloudCredentials.html">CloudCredentials</a>, <a href="json_BenchmarkResult.html">BenchmarkResult</a>, <a href="json_DeployResponse.html">DeployResponse</a>, <a href="json_ProvisionRequest.html">ProvisionRequest</a>, <a href="json_Script.html">Script</a>, <a href="json_KeyValueHolder.html">KeyValueHolder</a>, <a href="json_DeployRequest.html">DeployRequest</a>, <a href="json_MonitorringMessage.html">MonitorringMessage</a>, <a href="json_ProvisionResponse.html">ProvisionResponse</a></dd>
</dl>
<table class="table datatype-properties">
......@@ -89,7 +89,8 @@ class</p>
</span>
</td>
<td> <span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span>
</td>
</tr>
<tr>
......@@ -108,7 +109,8 @@ object is saved.</span>
<td> <span class="datatype-reference">number
</span>
</td>
<td> <span class="property-description">The object's creation date in unix time stamp</span>
<td> <span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span>
</td>
</tr>
</tbody>
......
......@@ -139,7 +139,8 @@ provisioner to request for cloud resources.</p>
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -152,7 +153,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -147,7 +147,8 @@
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -160,7 +161,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -120,7 +120,8 @@ request 1 we'll have 1</span>
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -133,7 +134,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -107,7 +107,8 @@
<td><span class="datatype-reference">string
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
<tr>
<td><span class="property-name">id</span></td>
......@@ -120,7 +121,8 @@ object is saved.</span></td>
<td><span class="property-name">timestamp</span></td>
<td><span class="datatype-reference">number
</span></td>
<td><span class="property-description">The object's creation date in unix time stamp</span></td>
<td><span class="property-description">The object's creation date in unix time stamp. It is created automatically.
No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -534,7 +534,8 @@ class]]>
<xs:annotation>
<xs:documentation>
<![CDATA[The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call]]>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST]]>
</xs:documentation>
</xs:annotation>
</xs:element>
......@@ -791,16 +792,16 @@ class]]>
<xs:complexContent>
<xs:extension base="ownedObject">
<xs:sequence>
<xs:element name="vmType" type="xs:string" minOccurs="0">
</xs:element>
<xs:element name="end" type="xs:dateTime" minOccurs="0">
<xs:element name="cloudDeploymentDomain" type="xs:string" minOccurs="0">
</xs:element>
<xs:element name="host" type="xs:string" minOccurs="0">
</xs:element>
<xs:element name="cloudDeploymentDomain" type="xs:string" minOccurs="0">
</xs:element>
<xs:element name="start" type="xs:dateTime" minOccurs="0">
</xs:element>
<xs:element name="vmType" type="xs:string" minOccurs="0">
</xs:element>
<xs:element name="end" type="xs:dateTime" minOccurs="0">
</xs:element>
<xs:element name="delta" type="xs:dateTime" minOccurs="0">
</xs:element>
</xs:sequence>
......
......@@ -144,12 +144,12 @@ Content-Type: application/json
<code class="prettyprint language-js">
[ {
&quot;cloudDeploymentDomain&quot; : &quot;us-east-1&quot;,
&quot;vmType&quot; : &quot;...&quot;,
&quot;start&quot; : 12345,
&quot;end&quot; : 12345,
&quot;delta&quot; : 12345,
&quot;host&quot; : &quot;147.228.242.58&quot;,
&quot;end&quot; : 12345,
&quot;cloudDeploymentDomain&quot; : &quot;us-east-1&quot;,
&quot;owner&quot; : &quot;user1&quot;,
&quot;id&quot; : &quot;58e3946e0fb4f562d84ba1ad&quot;,
&quot;timestamp&quot; : 1499793079011
......@@ -514,12 +514,12 @@ Content-Type: application/json
<code class="prettyprint language-js">
{
&quot;cloudDeploymentDomain&quot; : &quot;us-east-1&quot;,
&quot;vmType&quot; : &quot;...&quot;,
&quot;start&quot; : 12345,
&quot;end&quot; : 12345,
&quot;delta&quot; : 12345,
&quot;host&quot; : &quot;147.228.242.58&quot;,
&quot;end&quot; : 12345,
&quot;cloudDeploymentDomain&quot; : &quot;us-east-1&quot;,
&quot;owner&quot; : &quot;user1&quot;,
&quot;id&quot; : &quot;58e3946e0fb4f562d84ba1ad&quot;,
&quot;timestamp&quot; : 1499793079011
......
......@@ -193,7 +193,8 @@ used as a archive / log of ansible executions</p>
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -211,7 +211,8 @@ class</p>
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......@@ -219,11 +220,11 @@ the DAO saves the object based on the principal how made the call</span></td>
<p class="lead">Example</p>
<pre class="prettyprint language-xml example">&lt;b-----&gt;
&lt;vmType&gt;...&lt;/vmType&gt;
&lt;end&gt;...&lt;/end&gt;
&lt;host&gt;147.228.242.58&lt;/host&gt;
&lt;cloudDeploymentDomain&gt;us-east-1&lt;/cloudDeploymentDomain&gt;
&lt;host&gt;147.228.242.58&lt;/host&gt;
&lt;start&gt;...&lt;/start&gt;
&lt;vmType&gt;...&lt;/vmType&gt;
&lt;end&gt;...&lt;/end&gt;
&lt;delta&gt;...&lt;/delta&gt;
&lt;owner&gt;user1&lt;/owner&gt;
&lt;/b-----&gt;
......
......@@ -175,7 +175,8 @@ to request for resources.</p>
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -161,7 +161,8 @@ chosen deployment manager (for now only ansible)
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -201,7 +201,8 @@ chosen deployment manager (for now only ansible)
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -157,7 +157,8 @@ logging in VMs.</p>
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -105,7 +105,8 @@ abstract types such as TOSCA.</p>
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -211,7 +211,8 @@ class</p>
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -105,7 +105,8 @@ class</p>
</span>
</td>
<td> <span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span>
</td>
</tr>
</tbody>
......
......@@ -177,7 +177,8 @@ provisioner to request for cloud resources.</p>
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -191,7 +191,8 @@
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -160,7 +160,8 @@ deployment scale only swarm deployments are supported.</span>
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
......@@ -138,7 +138,8 @@
<td><span class="property-minMaxOccurs">0/1
</span></td>
<td><span class="property-description">The owner (username) for the particular object. This value is set when
the DAO saves the object based on the principal how made the call</span></td>
the DAO saves the object based on the principal who made the call.
It is created automatically. No need to set during a POST</span></td>
</tr>
</tbody>
</table>
......
/*
* Copyright 2017 S. Koulouzis, Wang Junchao, Huan Zhou, Yang Hu
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package nl.uva.sne.drip.api.exception;
import org.springframework.http.HttpStatus;
import org.springframework.web.bind.annotation.ResponseStatus;
/**
*
* @author S. Koulouzis
*/
@ResponseStatus(value = HttpStatus.NOT_FOUND, reason = "Cloud provider name can't be null")
public class NullCloudProviderException extends RuntimeException {
public NullCloudProviderException(String string) {
super(string);
}
public NullCloudProviderException() {
super();
}
}
......@@ -658,7 +658,7 @@ public class ProvisionService {
case "deploy_parameters":
String value = p.getValue();
String[] lines = value.split("\n");
if (value == null && value.length() < 2) {
if (value.length() < 2) {
throw new Exception("Provision failed");
}
for (String line : lines) {
......
......@@ -36,6 +36,7 @@ import org.springframework.web.bind.annotation.RestController;
import nl.uva.sne.drip.api.exception.BadRequestException;
import nl.uva.sne.drip.api.exception.KeyException;
import nl.uva.sne.drip.api.exception.NotFoundException;
import nl.uva.sne.drip.api.exception.NullCloudProviderException;
import nl.uva.sne.drip.api.exception.NullKeyException;
import nl.uva.sne.drip.api.service.CloudCredentialsService;
import nl.uva.sne.drip.api.service.KeyPairService;
......@@ -86,14 +87,9 @@ public class CloudCredentialsController {
if (cloudCredentials.getAccessKeyId() == null) {
throw new NullKeyException();
}
// List<String> ids = cloudCredentials.getkeyPairIDs();
// if (ids != null) {
// for (String id : ids) {
// if (keyService.findOne(id) == null) {
// throw new NullKeyException();
// }
// }
// }
if (cloudCredentials.getCloudProviderName() == null) {
throw new NullCloudProviderException();
}
cloudCredentials = cloudCredentialsService.save(cloudCredentials);
return cloudCredentials.getId();
}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment