Start line:  
End line:  

Snippet Preview

Snippet HTML Code

Stack Overflow Questions
  
  /*
   *  Copyright (C) 2010-2011 Oracle Corporation
   *
   *  This file is part of the VirtualBox SDK, as available from
   *  http://www.virtualbox.org.  This library is free software; you can
   *  redistribute it and/or modify it under the terms of the GNU Lesser General
   *  Public License as published by the Free Software Foundation, in version 2.1
   *  as it comes in the "COPYING.LIB" file of the VirtualBox SDK distribution.
  *  This library is distributed in the hope that it will be useful, but WITHOUT
  *  ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
  *  FITNESS FOR A PARTICULAR PURPOSE.  See the GNU Lesser General Public
  *  License for more details.
  *
  * IAppliance.java
  *
  * DO NOT EDIT! This is a generated file.
  * Generated from: src/VBox/Main/idl/VirtualBox.xidl (VirtualBox's interface definitions in XML)
  * Generator: src/VBox/Main/glue/glue-java.xsl
  */
 
 package org.virtualbox_4_2;
 
 import javax.xml.ws.*;
 import java.util.List;

Represents a platform-independent appliance in OVF format. An instance of this is returned by IVirtualBox.createAppliance(), which can then be used to import and export virtual machines within an appliance with VirtualBox. The OVF standard suggests two different physical file formats:
  1. If the appliance is distributed as a set of files, there must be at least one XML descriptor file that conforms to the OVF standard and carries an .ovf file extension. If this descriptor file references other files such as disk images, as OVF appliances typically do, those additional files must be in the same directory as the descriptor file.
  2. If the appliance is distributed as a single file, it must be in TAR format and have the .ova file extension. This TAR file must then contain at least the OVF descriptor files and optionally other files. At this time, VirtualBox does not not yet support the packed (TAR) variant; support will be added with a later version.
Importing an OVF appliance into VirtualBox as instances of IMachine involves the following sequence of API calls:
  1. Call IVirtualBox.createAppliance(). This will create an empty IAppliance object.
  2. On the new object, call read(java.lang.String) with the full path of the OVF file you would like to import. So long as this file is syntactically valid, this will succeed and fill the appliance object with the parsed data from the OVF file.
  3. Next, call interpret(), which analyzes the OVF data and sets up the contents of the IAppliance attributes accordingly. These can be inspected by a VirtualBox front-end such as the GUI, and the suggestions can be displayed to the user. In particular, the getVirtualSystemDescriptions() array contains instances of IVirtualSystemDescription which represent the virtual systems (machines) in the OVF, which in turn describe the virtual hardware prescribed by the OVF (network and hardware adapters, virtual disk images, memory size and so on). The GUI can then give the user the option to confirm and/or change these suggestions.
  4. If desired, call IVirtualSystemDescription.setFinalValues(java.util.List,java.util.List,java.util.List) for each virtual system (machine) to override the suggestions made by the interpret() routine.
  5. Finally, call importMachines(java.util.List) to create virtual machines in VirtualBox as instances of IMachine that match the information in the virtual system descriptions. After this call succeeded, the UUIDs of the machines created can be found in the getMachines() array attribute.
Exporting VirtualBox machines into an OVF appliance involves the following steps:
  1. As with importing, first call IVirtualBox.createAppliance() to create an empty IAppliance object.
  2. For each machine you would like to export, call IMachine.export(org.virtualbox_4_2.IAppliance,java.lang.String) with the IAppliance object you just created. Each such call creates one instance of IVirtualSystemDescription inside the appliance.
  3. If desired, call IVirtualSystemDescription.setFinalValues(java.util.List,java.util.List,java.util.List) for each virtual system (machine) to override the suggestions made by the IMachine.export(org.virtualbox_4_2.IAppliance,java.lang.String) routine.
  4. Finally, call write(java.lang.String,java.lang.Boolean,java.lang.String) with a path specification to have the OVF file written.
Interface ID: {3059CF9E-25C7-4F0B-9FA5-3C42E441670B}
 
 public class IAppliance extends IUnknown {
 
     public IAppliance(String wrappedVboxPortType port) {
           super(wrappedport);
     }
Path to the main file of the OVF appliance, which is either the .ovf or the .ova file passed to read(java.lang.String) (for import) or write(java.lang.String,java.lang.Boolean,java.lang.String) (for export). This attribute is empty until one of these methods has been called.

Returns:
String
 
     public String getPath() {
       try {
          String retVal = .iApplianceGetPath();
          return retVal;
      } catch (InvalidObjectFaultMsg e) {
           throw new VBoxException(ee.getMessage());
      } catch (RuntimeFaultMsg e) {
           throw new VBoxException(ee.getMessage());
     }
    }
Array of virtual disk definitions. One such description exists for each disk definition in the OVF; each string array item represents one such piece of disk information, with the information fields separated by tab (\\t) characters. The caller should be prepared for additional fields being appended to this string in future versions of VirtualBox and therefore check for the number of tabs in the strings returned. In the current version, the following eight fields are returned per string in the array:
  1. Disk ID (unique string identifier given to disk)
  2. Capacity (unsigned integer indicating the maximum capacity of the disk)
  3. Populated size (optional unsigned integer indicating the current size of the disk; can be approximate; -1 if unspecified)
  4. Format (string identifying the disk format, typically "http://www.vmware.com/specifications/vmdk.html#sparse")
  5. Reference (where to find the disk image, typically a file name; if empty, then the disk should be created on import)
  6. Image size (optional unsigned integer indicating the size of the image, which need not necessarily be the same as the values specified above, since the image may be compressed or sparse; -1 if not specified)
  7. Chunk size (optional unsigned integer if the image is split into chunks; presently unsupported and always -1)
  8. Compression (optional string equalling "gzip" if the image is gzip-compressed)

Returns:
List<String>
    public List<StringgetDisks() {
      try {
         List<StringretVal = .iApplianceGetDisks();
         return retVal;
     } catch (InvalidObjectFaultMsg e) {
          throw new VBoxException(ee.getMessage());
     } catch (RuntimeFaultMsg e) {
          throw new VBoxException(ee.getMessage());
     }
    }
Array of virtual system descriptions. One such description is created for each virtual system (machine) found in the OVF. This array is empty until either interpret() (for import) or IMachine.export(org.virtualbox_4_2.IAppliance,java.lang.String) (for export) has been called.

Returns:
List<org.virtualbox_4_2.IVirtualSystemDescription>
      try {
         return Helper.wrap(org.virtualbox_4_2.IVirtualSystemDescription.classretVal);
     } catch (InvalidObjectFaultMsg e) {
          throw new VBoxException(ee.getMessage());
     } catch (RuntimeFaultMsg e) {
          throw new VBoxException(ee.getMessage());
     }
    }
Contains the UUIDs of the machines created from the information in this appliances. This is only relevant for the import case, and will only contain data after a call to importMachines(java.util.List) succeeded.

Returns:
List<String>
    public List<StringgetMachines() {
      try {
         List<StringretVal = .iApplianceGetMachines();
         return retVal;
     } catch (InvalidObjectFaultMsg e) {
          throw new VBoxException(ee.getMessage());
     } catch (RuntimeFaultMsg e) {
          throw new VBoxException(ee.getMessage());
     }
    }
    public static IAppliance queryInterface(IUnknown obj) {
       return obj == null ?  null : new IAppliance(obj.getWrapped(), obj.getRemoteWSPort());
    }
Reads an OVF file into the appliance object. This method succeeds if the OVF is syntactically valid and, by itself, without errors. The mere fact that this method returns successfully does not mean that VirtualBox supports all features requested by the appliance; this can only be examined after a call to interpret().

Parameters:
file Name of appliance file to open (either with an .ovf or .ova extension, depending on whether the appliance is distributed as a set of files or as a single file, respectively).
Returns:
Progress object to track the operation completion.
    public org.virtualbox_4_2.IProgress read(String file) {
      try {
        String     retVal;
        retVal = .iApplianceRead(file);
        return (retVal.length() > 0) ? new org.virtualbox_4_2.IProgress(retVal) : null;
     } catch (InvalidObjectFaultMsg e) {
          throw new VBoxException(ee.getMessage());
     } catch (RuntimeFaultMsg e) {
          throw new VBoxException(ee.getMessage());
     }
    }
Interprets the OVF data that was read when the appliance was constructed. After calling this method, one can inspect the getVirtualSystemDescriptions() array attribute, which will then contain one IVirtualSystemDescription for each virtual machine found in the appliance. Calling this method is the second step of importing an appliance into VirtualBox; see IAppliance for an overview. After calling this method, one should call getWarnings() to find out if problems were encountered during the processing which might later lead to errors.
    public void interpret() {
      try {
        .iApplianceInterpret();
     } catch (InvalidObjectFaultMsg e) {
          throw new VBoxException(ee.getMessage());
     } catch (RuntimeFaultMsg e) {
          throw new VBoxException(ee.getMessage());
     }
    }
Imports the appliance into VirtualBox by creating instances of IMachine and other interfaces that match the information contained in the appliance as closely as possible, as represented by the import instructions in the getVirtualSystemDescriptions() array. Calling this method is the final step of importing an appliance into VirtualBox; see IAppliance for an overview. Since importing the appliance will most probably involve copying and converting disk images, which can take a long time, this method operates asynchronously and returns an IProgress object to allow the caller to monitor the progress. After the import succeeded, the UUIDs of the IMachine instances created can be retrieved from the getMachines() array attribute.

Parameters:
options Options for the importing operation.
Returns:
Progress object to track the operation completion.
      try {
        String     retVal;
        return (retVal.length() > 0) ? new org.virtualbox_4_2.IProgress(retVal) : null;
     } catch (InvalidObjectFaultMsg e) {
          throw new VBoxException(ee.getMessage());
     } catch (RuntimeFaultMsg e) {
          throw new VBoxException(ee.getMessage());
     }
    }
Returns a IVFSExplorer object for the given URI.

Parameters:
aUri The URI describing the file system to use.
      try {
        String     retVal;
        retVal = .iApplianceCreateVFSExplorer(aUri);
        return (retVal.length() > 0) ? new org.virtualbox_4_2.IVFSExplorer(retVal) : null;
     } catch (InvalidObjectFaultMsg e) {
          throw new VBoxException(ee.getMessage());
     } catch (RuntimeFaultMsg e) {
          throw new VBoxException(ee.getMessage());
     }
    }
Writes the contents of the appliance exports into a new OVF file. Calling this method is the final step of exporting an appliance from VirtualBox; see IAppliance for an overview. Since exporting the appliance will most probably involve copying and converting disk images, which can take a long time, this method operates asynchronously and returns an IProgress object to allow the caller to monitor the progress.

Parameters:
format Output format, as a string. Currently supported formats are "ovf-0.9", "ovf-1.0" and "ovf-2.0"; future versions of VirtualBox may support additional formats.
manifest Indicate if the optional manifest file (.mf) should be written. The manifest file is used for integrity checks prior import.
path Name of appliance file to open (either with an .ovf or .ova extension, depending on whether the appliance is distributed as a set of files or as a single file, respectively).
Returns:
Progress object to track the operation completion.
    public org.virtualbox_4_2.IProgress write(String formatBoolean manifestString path) {
      try {
        String     retVal;
        retVal = .iApplianceWrite(formatmanifestpath);
        return (retVal.length() > 0) ? new org.virtualbox_4_2.IProgress(retVal) : null;
     } catch (InvalidObjectFaultMsg e) {
          throw new VBoxException(ee.getMessage());
     } catch (RuntimeFaultMsg e) {
          throw new VBoxException(ee.getMessage());
     }
    }
Returns textual warnings which occurred during execution of interpret().
    public List<StringgetWarnings() {
      try {
        List<String>     retVal;
        retVal = .iApplianceGetWarnings();
        return retVal;
     } catch (InvalidObjectFaultMsg e) {
          throw new VBoxException(ee.getMessage());
     } catch (RuntimeFaultMsg e) {
          throw new VBoxException(ee.getMessage());
     }
    }
New to GrepCode? Check out our FAQ X