I'm curious if anyone has tried ViJava with vSphere 6?
I did and immediately hit problems with the InventoryNavigator class. It did not work at all for me, so I had to replace my code that used InventoryNavigator with straight PropertyCollector code.
Anyone else run into this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Lee,
I assume you are the same Lee from github, if so can you update the bug we were working on at github with the errors you were getting? I have functional support for 6 and havent had any issues with the inventory navigator so if you will update that issue on github with any stack traces or what ever Ill try to fix it if I can reproduce it. https://github.com/yavijava/yavijava/issues/29 I wont be able to push the fixes until I hear back from vmware about the nda status, but at least I can have the fix ready to go..
Last edit: errr 2015-06-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I maintain an active fork of this project on github called yavijava https://github.com/yavijava/yavijava Ive been working on support for 6 as well as several other interesting features. The project is available in maven and I welcome any help anyone is willing to offer.
Last edit: errr 2015-06-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi All,
I have one simple vsphere plugin with vijava 5.5 and in vcenter 5.5.. Now I upgraded my vcenter 5.5 to vcenter 6.0. And then, while i run my plugin, its not working. I couldnt fetch anything from vijava, like datacentre, host, datastores..
please somebody suggest me..
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If youre using code that uses the InventoryNavigator its going to fail on 6.0 it is hard coded to look for version 4 or 5 of the api, and when it finds version 6 it loads the wrong traversal specs. I fixed that in yavijava, Ive also got a 6.0 beta release ready. You can find out more here: http://www.errr-online.com/index.php/2015/05/26/yavijava-6-0-beta-release-ready-for-vsphere-6-0/
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm using the InventoryNavigator with vijava 5.1 against esxi 6.0 and I'm not having a problem. I'm calling the searchManagedEntities method with vcente 6.0 and searchManagedEntity method when connecting to a single host. In both cases I'm searching the root folder and it seems to be working.
Do you have a specific use case you could share that would break? I'm just wondering if there an an environmental aspect to this issue. If so I want to handle that case as well and maybe I need to upgradae to yavijava afterall.
Thanks,
Damon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
Last VI Java release was in the fall 2013 and labeled as Beta support for vSphere 5.5.
vSphere 6 will be released in the spring of 2015 by VMWare.
If there are plans to include a support for vSphere 6 ?
Thank you,
Boris.
I'm curious if anyone has tried ViJava with vSphere 6?
I did and immediately hit problems with the InventoryNavigator class. It did not work at all for me, so I had to replace my code that used InventoryNavigator with straight PropertyCollector code.
Anyone else run into this?
Hi Lee,
I assume you are the same Lee from github, if so can you update the bug we were working on at github with the errors you were getting? I have functional support for 6 and havent had any issues with the inventory navigator so if you will update that issue on github with any stack traces or what ever Ill try to fix it if I can reproduce it. https://github.com/yavijava/yavijava/issues/29 I wont be able to push the fixes until I hear back from vmware about the nda status, but at least I can have the fix ready to go..
Last edit: errr 2015-06-03
Hi Boris,
I maintain an active fork of this project on github called yavijava https://github.com/yavijava/yavijava Ive been working on support for 6 as well as several other interesting features. The project is available in maven and I welcome any help anyone is willing to offer.
Last edit: errr 2015-06-03
Hi All,
I have one simple vsphere plugin with vijava 5.5 and in vcenter 5.5.. Now I upgraded my vcenter 5.5 to vcenter 6.0. And then, while i run my plugin, its not working. I couldnt fetch anything from vijava, like datacentre, host, datastores..
please somebody suggest me..
If youre using code that uses the InventoryNavigator its going to fail on 6.0 it is hard coded to look for version 4 or 5 of the api, and when it finds version 6 it loads the wrong traversal specs. I fixed that in yavijava, Ive also got a 6.0 beta release ready. You can find out more here: http://www.errr-online.com/index.php/2015/05/26/yavijava-6-0-beta-release-ready-for-vsphere-6-0/
I'm using the InventoryNavigator with vijava 5.1 against esxi 6.0 and I'm not having a problem. I'm calling the searchManagedEntities method with vcente 6.0 and searchManagedEntity method when connecting to a single host. In both cases I'm searching the root folder and it seems to be working.
Do you have a specific use case you could share that would break? I'm just wondering if there an an environmental aspect to this issue. If so I want to handle that case as well and maybe I need to upgradae to yavijava afterall.
Thanks,
Damon
I used InventoryNavigator with vijava5.5b against vCenter 6.0 it is working as expected. Am i missing something here?
I'm thinking there's an environmental aspect to this that I'd need to recreate to see the issue.