<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/vijava/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/vijava/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/vijava/feature-requests/</id><updated>2012-06-28T22:58:06Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>Need for the vim25 library to be serializable</title><link href="https://sourceforge.net/p/vijava/feature-requests/27/" rel="alternate"/><published>2012-06-28T22:58:06Z</published><updated>2012-06-28T22:58:06Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net9b265d27f2d1d1492398cf6bdcf656f906279ef7</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It would be nice if the library can be made serializable.  This allows us to take a snapshot at a customers site and bring the snapshot back to the office to analyze / debug any of our code that not behaving.  The vim25 library distributed by VMware is serializable.  If there is a performance issue related to this, it would be nice if there were two versions of the library.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Support for VMWare 5.1 Beta</title><link href="https://sourceforge.net/p/vijava/feature-requests/26/" rel="alternate"/><published>2012-06-06T21:30:44Z</published><updated>2012-06-06T21:30:44Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netc47618498ad3c21831e39cef112e084c2964f55c</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Support VIJAVA with VMWare 5.1 Beta&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Need change in output parameters of searchManaged Entities</title><link href="https://sourceforge.net/p/vijava/feature-requests/25/" rel="alternate"/><published>2012-01-21T03:30:45Z</published><updated>2012-01-21T03:30:45Z</updated><author><name>Guru Prashanth</name><uri>https://sourceforge.net/u/guru1306/</uri></author><id>https://sourceforge.net8b50dd2e7fa0afe145bbde58a9517844958fd531</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The function  mentioned below returns only  ManagedEntity though it retrieves the properties of the ManagedEntity. &lt;/p&gt;
&lt;p&gt;public ManagedEntity[] searchManagedEntities(String[][] typeinfo, boolean recurse ) throws InvalidProperty, RuntimeFault, RemoteException&lt;/p&gt;
&lt;p&gt;We can return it as a Map containing ManagedEntity and HashTable( ObjectContents for the properties  ) for each entry.So the user need not call again the  retrieveproperties function in propertycollectorutil to get the properties of the managed Entity&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Reuse SSLSocketFactory</title><link href="https://sourceforge.net/p/vijava/feature-requests/24/" rel="alternate"/><published>2012-01-20T14:11:24Z</published><updated>2012-01-20T14:11:24Z</updated><author><name>Shai Benjamin</name><uri>https://sourceforge.net/u/sheyeh/</uri></author><id>https://sourceforge.net91c20de94c20a7b3e083414817980cda987b4c03</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;WCClient uses a new instance of SSLSocketFactory every time it connects to VC. As a result, sockets cannot be reused. There is also a small performance issue that trustAllHttpsCertificates() is executed upon each connection when it actually needs to be executed only once per the lifetime of the application.&lt;/p&gt;
&lt;p&gt;Suggested code changes:&lt;/p&gt;
&lt;p&gt;private static volatile boolean initialized = false; // new code&lt;/p&gt;
&lt;p&gt;private static void trustAllHttpsCertificates() &lt;br /&gt;
throws NoSuchAlgorithmException, KeyManagementException&lt;br /&gt;
{&lt;br /&gt;
      if (initialized) return; // new code&lt;br /&gt;
      initialized = true; // new code&lt;br /&gt;
      TrustManager[] trustAllCerts = new TrustManager[1]; &lt;br /&gt;
      trustAllCerts[0] = new TrustAllManager(); &lt;br /&gt;
      SSLContext sc = SSLContext.getInstance("SSL"); &lt;br /&gt;
      sc.init(null, trustAllCerts, null); &lt;br /&gt;
      HttpsURLConnection.setDefaultSSLSocketFactory(sc.getSocketFactory());&lt;br /&gt;
}&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Maintain original exception upon posting xml</title><link href="https://sourceforge.net/p/vijava/feature-requests/23/" rel="alternate"/><published>2012-01-10T00:09:41Z</published><updated>2012-01-10T00:09:41Z</updated><author><name>Sergey Sudakovich</name><uri>https://sourceforge.net/u/ssudakov/</uri></author><id>https://sourceforge.net477775e4c3c19daf976330ee34b7c89561e00fcc</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;As it is done right now when the message is posted:&lt;br /&gt;
public Element invoke(String methodName, Argument[] paras) throws RemoteException&lt;br /&gt;
{&lt;br /&gt;
...............  &lt;br /&gt;
try &lt;br /&gt;
{&lt;br /&gt;
is = post(soapMsg);&lt;br /&gt;
SAXReader reader = new SAXReader();&lt;br /&gt;
Document doc = reader.read(is);&lt;br /&gt;
        root = doc.getRootElement();&lt;br /&gt;
} catch (Exception e) &lt;br /&gt;
{&lt;br /&gt;
throw new RemoteException("VI SDK invoke exception:" + e);&lt;br /&gt;
}&lt;/p&gt;
&lt;p&gt;Any kind of exception is wrapped into RemoteException and the exception is lost. It would be nice if instead of &lt;br /&gt;
throw new RemoteException("VI SDK invoke exception:" + e);&lt;br /&gt;
we could have&lt;br /&gt;
throw new RemoteException("VI SDK invoke exception:" + e, e);&lt;/p&gt;
&lt;p&gt;So if need be the original exception is maintained.&lt;br /&gt;
This request came in to existence due to this situation (&lt;a href="https://sourceforge.net/projects/vijava/forums/forum/826592/topic/4937834"&gt;https://sourceforge.net/projects/vijava/forums/forum/826592/topic/4937834&lt;/a&gt;)&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Allow configuring timeouts in ServiceInstance constructor</title><link href="https://sourceforge.net/p/vijava/feature-requests/22/" rel="alternate"/><published>2011-07-15T21:53:52Z</published><updated>2011-07-15T21:53:52Z</updated><author><name>Michael Matczynski</name><uri>https://sourceforge.net/u/mmatczynski/</uri></author><id>https://sourceforge.net10558676c95dc5d9b808cf9294ffc59b5412dab1</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;In vijava 2.1 support was added to access timeout values on an existing ServiceInstance.&lt;/p&gt;
&lt;p&gt;Per discussion on Steve's blog it sounds like there is a need for additionally specifying the timeout values before any connection to the server is made:&lt;br /&gt;
&lt;a href="http://www.doublecloud.org/2011/03/how-to-set-up-connection-timeout-in-vi-java-api/" rel="nofollow"&gt;http://www.doublecloud.org/2011/03/how-to-set-up-connection-timeout-in-vi-java-api/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;We can pass in arguments via the constructor or maybe add a context object that can hold miscellaneous parameters like timeout values?&lt;/p&gt;
&lt;p&gt;Thanks!&lt;br /&gt;
Mike&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>allow user to provide WSClient</title><link href="https://sourceforge.net/p/vijava/feature-requests/21/" rel="alternate"/><published>2011-01-13T18:35:14Z</published><updated>2011-01-13T18:35:14Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net5aff5713e0f93171a25f31f1caaf6be290d07fd8</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I'd like to use my own implementation of WSClient.  I can do this with reflection, but it would be nice not to.&lt;/p&gt;
&lt;p&gt;Are you ok with something like below?&lt;/p&gt;
&lt;p&gt;1. remove final modifier from WSClientl&lt;br /&gt;
2. Change WSClient to an interface (optional)&lt;br /&gt;
3. open a constructor on ServiceInstance where we can specify a WSClient object&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>can Event object implement Serializable in VIJava</title><link href="https://sourceforge.net/p/vijava/feature-requests/20/" rel="alternate"/><published>2010-10-01T21:48:30Z</published><updated>2010-10-01T21:48:30Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net8527e1157c4f3491d9cd85dd32bbb846afdd9f06</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Vishal says:&lt;br /&gt;
October 1, 2010 at 12:54 pm&lt;br /&gt;
Steve,&lt;/p&gt;
&lt;p&gt;can you make the Event Object implement Serializable, we are internally using these event objects on our JMS bus, and those objects must be Serializable, So to solve it we are right now converting all of event content to local Serializable objects. and publishing them.&lt;/p&gt;
&lt;p&gt;Steve Jin says:&lt;br /&gt;
October 1, 2010 at 2:25 pm&lt;br /&gt;
Hi Vishal,&lt;/p&gt;
&lt;p&gt;Please file a feature request from the vijava tracker: &lt;a href="https://sourceforge.net/tracker/?group"&gt;https://sourceforge.net/tracker/?group&lt;/a&gt;_id=228007. I will get to it later.&lt;/p&gt;
&lt;p&gt;Steve&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>support clone() for data objects</title><link href="https://sourceforge.net/p/vijava/feature-requests/19/" rel="alternate"/><published>2010-09-17T20:11:33Z</published><updated>2010-09-17T20:11:33Z</updated><author><name/><uri>https://sourceforge.net</uri></author><id>https://sourceforge.netfdfc0f16627682df20730bff1552e766cc6ac92e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I have a few places where either I:&lt;br /&gt;
(1) have to return a VIM data object to a caller and want to give him a defensive copy rather than a reference to my internal state.&lt;br /&gt;
or&lt;br /&gt;
(2) have a VIM data object that I want to duplicate but don't know the real type. E.g., I want to add a second NIC to a VM, but don't know which subclass&lt;br /&gt;
of VirtualEthernetCard is the best to use for the guest/hypervisor combination. So I'd like to duplicate his first NIC, change the unit number, and&lt;br /&gt;
pass it right back into VM.reconfigure.&lt;/p&gt;
&lt;p&gt;So it'd be great if DynamicData implemented Cloneable, and used the existing DeepCopier to implement clone().&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>remote accessors should document and throw RemoteException</title><link href="https://sourceforge.net/p/vijava/feature-requests/18/" rel="alternate"/><published>2010-09-17T17:23:22Z</published><updated>2010-09-17T17:23:22Z</updated><author><name/><uri>https://sourceforge.net</uri></author><id>https://sourceforge.netc30c48dd8607def77304975b7e556707352425fd</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;One of the subtle aspects to using proxies like VI Java is knowing which calls are remote (eg, VirtualMachine.getName) and which are local&lt;br /&gt;
(eg, VirtualMachineConfigInfo.getName). Remote calls (in addition to the performance difference) have extra failure modes that may need&lt;br /&gt;
to be dealt with. It would help greatly if the declarations for remote calls always included a throws clause for RemoteException (and actually&lt;br /&gt;
threw it).&lt;/p&gt;
&lt;p&gt;All the modifying calls in VI Java have this right, but the accessors all go through ManagedObject.retrieveObjectProperties, which does this:&lt;br /&gt;
try&lt;br /&gt;
{&lt;br /&gt;
objs = pc.retrieveProperties(new PropertyFilterSpec[] { pfSpec });&lt;br /&gt;
} catch(Exception e)&lt;br /&gt;
{&lt;br /&gt;
throw new RuntimeException(e);&lt;br /&gt;
}&lt;br /&gt;
So a connection/session failure with vCenter will cause a RuntimeException to be thrown when calling an accessor. This means&lt;br /&gt;
that software that wants to re-establish a session and re-try the operation has to catch RuntimeException, which is generally&lt;br /&gt;
not a good idea in Java. My own code currently relies on looking at the getCause of the RuntimeException to see if it&lt;br /&gt;
is a RemoteException and therefore retryable.&lt;/p&gt;
&lt;p&gt;So please change the above to let RemoteException through. I realize this means changing perhaps hundreds of APIs to&lt;br /&gt;
include RemoteException in the throws clause, but I think it will help VI Java users produce better software.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>