From 677cdfaafa4f9f0bcfca23976674bb6d12cf4d57 Mon Sep 17 00:00:00 2001 From: Aled Sage Date: Fri, 16 Mar 2012 17:28:20 +0000 Subject: [PATCH] Issue #830: added VdcClient.upload comment about file size of -1 --- .../org/jclouds/vcloud/director/v1_5/features/VdcClient.java | 3 +++ 1 file changed, 3 insertions(+) diff --git a/labs/vcloud-director/src/main/java/org/jclouds/vcloud/director/v1_5/features/VdcClient.java b/labs/vcloud-director/src/main/java/org/jclouds/vcloud/director/v1_5/features/VdcClient.java index 57a664e3db..1370411731 100644 --- a/labs/vcloud-director/src/main/java/org/jclouds/vcloud/director/v1_5/features/VdcClient.java +++ b/labs/vcloud-director/src/main/java/org/jclouds/vcloud/director/v1_5/features/VdcClient.java @@ -134,6 +134,9 @@ public interface VdcClient { * The status of vApp template will be NOT_READY(0) until the ovf and all disks are uploaded * to the transfer site. After this a task will run on the vApp template uploading. * + * Note that the empty vApp template's getFiles() returns a file of size -1 after step one above, + * because the descriptor.ovf does not yet exist. + * * @return a VAppTemplate resource which will contain a task. * The user should should wait for this task to finish to be able to use the VAppTemplate. */