Announcing VI Java API 5.0 Beta

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.

Lost VMs or Containers? Too Many Consoles? Too Slow GUI? Time to learn how to "Google" and manage your VMware and clouds in a fast and secure HTML5 App.

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.

This entry was posted in vSphere API and tagged . Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.


  1. Rosanna
    Posted August 30, 2011 at 2:00 pm | Permalink

    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. Posted August 30, 2011 at 3:15 pm | Permalink

    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
    Posted September 7, 2011 at 3:44 am | Permalink

    Thanks Steve for the 5.0 version of vijava. Can you also add it to so that mvn users can directly use it from there.

  4. Posted September 7, 2011 at 12:47 pm | Permalink

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


3 Trackbacks

  • By VIX Implementation in vSphere Java API | on September 12, 2011 at 11:47 pm

    […] designing Java API for the VIX in VI Java API 5.0 beta, I made some changes to make it more object-oriented, and as a result easier to use. So if you use […]

  • By Missing ArrayOfDatastoreEventArgument | on September 19, 2011 at 1:06 am

    […] the vSphere Java API 5.0 beta was released, I got a very interesting bug that I think is worthwhile to share with the community. Note that I […]

  • By VI Java API 5.0 GA Released | on October 2, 2011 at 10:47 pm

    […] plus month since I pushed out the beta code which has since been downloaded more than 700 times. As promised, I am happy to announce the GA of VI Java API 5.0 today. This is the fourth major release after […]

Post a Comment

Your email is never published nor shared. Required fields are marked *


You may use these HTML tags and attributes <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>


    My company has created products like vSearch ("Super vCenter"), vijavaNG APIs, EAM APIs, ICE tool. We also help clients with virtualization and cloud computing on customized development, training. Should you, or someone you know, need these products and services, please feel free to contact me: steve __AT__

    Me: Steve Jin, VMware vExpert who authored the VMware VI and vSphere SDK by Prentice Hall, and created the de factor open source vSphere Java API while working at VMware engineering. Companies like Cisco, EMC, NetApp, HP, Dell, VMware, are among the users of the API and other tools I developed for their products, internal IT orchestration, and test automation.