Home > vSphere API > Announcing VI Java API 5.0 Beta

Announcing VI Java API 5.0 Beta

August 25th, 2011 Leave a comment Go to comments

Now that vSphere 5 just GAed today, I am happy to announce the public beta of VI Java API Crescendo release. Based on the feedbacks I got from the community, especially William Lam, I decided the new version to be 5.0 beta so that we can sync up with the vSphere 5.0.

This beta code has been used internally and externally in various projects for months. Still, I would like to have one month or so beta phase for your feedbacks. Please feel free to file a bug here. As always, we strive for the best quality, because I know you rely on this API for managing your mission critical infrastructures.

Time to learn how to "Google" and manage your VMware and clouds in a fast and secure


The biggest change in this new release is the vSphere 5.0 support. If you haven’t read what’s new in vSphere API 5.0, it’s time to do so. The overall structure of the API is the same as before and 100% compatible with previous versions. As a user of the API, you won’t feel much difference except that you find more managed object types and additional methods on existing ones.

There are several hundreds of new files and changes to existing ones. While I was committing them to the repository, I found the Subversion plugin for Eclipse broke with confusing error messages about .svn\tmp\tempfile.tmp file. After searching Web and experimenting by myself, it turned out to a limit on the number of files to be committed at one batch. With several trials, I found the magic number to be 100. Sometimes it’s lower, which made me think McAfee antivirus may had contributed to the problem one way or the other.

Anyway, the download is there for you – Go downlad it and give it a try. If you like it, don’t forget to tell others.

Categories: vSphere API Tags:
  1. Rosanna
    August 30th, 2011 at 14:00 | #1

    Are the javadocs for the beta available?

    I was wondering if you could add the following methods to WSClient. I use them to get around hanging problems.

    public static void setGlobalReadTimeout(int timeoutMilliSec);
    public static void setGlobalConnectTimeout(int timeoutMilliSec);

    These are analogous to the set*Timeout() instance methods and will be used in post() if the connectTimeout/readTimeout has not been set. I can send you my diff if you want.


  2. August 30th, 2011 at 15:15 | #2

    Thanks Rosanna,

    There is no javadoc but it’s very close to the vSphere API reference.

    Thanks for the suggestion. Please please send me the diff.


  3. Abhi
    September 7th, 2011 at 03:44 | #3

    Thanks Steve for the 5.0 version of vijava. Can you also add it to http://mvnrepository.com/artifact/org.jvnet.hudson/vijava so that mvn users can directly use it from there.

  4. September 7th, 2011 at 12:47 | #4

    Had plan to make it Maven ready. Will continue it later.


  1. September 12th, 2011 at 23:47 | #1
  2. September 19th, 2011 at 01:06 | #2
  3. October 2nd, 2011 at 22:47 | #3