Home > vSphere API > VI Java API 5.0 GA Released

VI Java API 5.0 GA Released

October 2nd, 2011 Leave a comment Go to comments

It’s been one 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 1.0, 2.0, and 2.1 which are all shipped on time. Predictability is important for commercial products, even so for open source projects like this. I think we’ve demonstrated it in the past three and half years since the first release in May 2008.

As mentioned in beta announcement, I’ve decided to jump the number to 5.0 to better align with vSphere versioning which is now 5.0. I expect to sync up with future vSphere releases in both features and version numbers.

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


Now, let’s get to the technical side: what’s fixed from beta? Here are several of them:

  • Bug 3042167: xml characters not escaped.
  • Bug 3406597: Broken UTF-8 handling in WSClient class
  • Bug 3400964 API is missing  the type ArrayOfDatastoreEventArgument
  • Bug 3405278 Client REST API breaks with vSphere 4.1 u1

I would like to thank my manager Rich Hogan for sponsoring some of my time to work on this release, VMware product management Mahesh Ramachandran and Tsun Tsun Ho for their support, and several internal and external teams who helped to give me many feedbacks and try the alpha and beta code.

Thanks also go to our community who has been very supportive and by trying the API, reporting bugs, and helping each other in the community forum. This is really encouraging experience for me.

Ready to give 5.0 a try? Check it out here.

Categories: vSphere API Tags:
  1. guillaume Le Louët
    October 3rd, 2011 at 07:33 | #1

    hello Steve.
    I encapsulated the project in a maven artifact and deployed it on our public repo :

    add the following repo to your pom :

    entropy repo
    repository of the entropy project

    and the following dependency :


    and you’re done :)
    The repo contains the dependency cim-client ‘s jar (using maven nothing special is required), and the other dependencies of vijava (dom4j, javax-servlet, mail) are correctly handled by maven using the declaration of the pom.xml .

  2. guillaume Le Louët
  3. guillaume Le Louët
    October 3rd, 2011 at 07:59 | #3
  4. April 23rd, 2012 at 17:10 | #4

    Is there a bug with “printExtraDiskFileInfo((VmDiskFileInfo)fis[j]);” in code example for “SearchDatastore.java”? It’s only returning NULL values? The environment is all version 5, vcenter and esx hosts.

  1. No trackbacks yet.