Comments on: VIJava Browser – A Great Tool To Recommend!

By: yan

yan — Thu, 19 Aug 2010 09:27:15 +0000

Hi Steve,
You are right,my lib is messed up with a vim25 jar file from AXIS stub.

By: Steve Jin

Steve Jin — Thu, 19 Aug 2010 05:23:55 +0000

Hi Vishal,

Just wrote a comprehensive blog: http://www.doublecloud.org/2010/08/how-to-get-event-type-with-vsphere-api/. Hope you find it helpful.

Steve

By: Vishal

Vishal — Tue, 17 Aug 2010 17:47:45 +0000

Steve,

Any reason why the severity is skipped from the Event object? in our NMS tool we need to set the severity for each event, and i was planning to have it same as your Enum – EventEventSeverity. we are currently processing 87 Events, it would be tough to parse the event name to get the severity.

is it possible to add severity to the event object?

Thanks
Vishal

By: Steve Jin

Steve Jin — Tue, 17 Aug 2010 05:23:23 +0000

Hi Vishal,
I am going to GA the 2.1 very soon. You can either pick the source code from SVN right now or wait a little bit. I prefer the former because you can double check if the problem is solved. Please update the bug tracker upon validation.
As you said, the event object itself does not have field for the type, but the concrete event (subtypes of Event) does indicate something. For example, HostEnableAdminFailedEvent tells the nature of the event by its type name. Hope it helps.
Steve

By: Vishal

Vishal — Mon, 16 Aug 2010 23:04:38 +0000

Thanks Steve, for a quick fix, I am assuming i can pick it up in a patch release of 4.1.

One more question.

I see that when viClient reports events there is a type field {error|info|warning}, how do i get this info along with the event object, seems like event object doesnt have a severity or type field.

Thanks
Vishal

By: Steve Jin

Steve Jin — Mon, 16 Aug 2010 15:01:14 +0000

Hi Yan,

It’s most likely a classpath issue with AXIS generated stub included in your classpath. Remove it and try again.

-Steve

By: yan

yan — Mon, 16 Aug 2010 08:32:53 +0000

Hi Setve,

when I run this tools,it throw following error:
Exception occurred during event dispatching:
java.lang.InstantiationError: com.vmware.vim25.VimPortType
at com.vmware.vim25.mo.ServiceInstance.(ServiceInstance.java:82)
at com.vmware.vim25.mo.ServiceInstance.(ServiceInstance.java:69)
at vijavaBrowser.LoginDialog.onOk(LoginDialog.java:256)

I used this version vi java api:
vijava2120100715.jar

And I also have the same error when writing my own class when only invoke this constructor method:

public class newtest {

public static void main(String[] args) throws RemoteException, MalformedURLException {
ServiceInstance si = new ServiceInstance(new URL(“https://10.10.10.147/sdk”), “root”, “password”, true);
}

}

It is the same code as in the tool source code, I can not figure out why,can you help me? Cause if I can not have this “ServiceInstance” I can do nothing

By: Steve Jin

Steve Jin — Fri, 06 Aug 2010 23:03:31 +0000

Thanks Vishal for filing the bug: https://sourceforge.net/tracker/index.php?func=detail&aid=3040909&group_id=228007&atid=1073396. It’s fixed. Check the bug record for more info.

Steve

By: Steve Jin

Steve Jin — Fri, 06 Aug 2010 18:29:17 +0000

Hi Vishal,

This is a bug in vijava api. Could you please file a bug: https://sourceforge.net/tracker/?group_id=228007

Thanks!

Steve

By: Vishal

Vishal — Fri, 06 Aug 2010 16:40:37 +0000

Fails to browse the HostProfiles, from HostProfileManager.
Got the following exception.
Caused by: java.lang.ClassCastException: [Lcom.vmware.vim25.ManagedObjectReference; cannot be cast to [Lcom.vmware.vim25.mo.Profile;
at com.vmware.vim25.mo.ProfileManager.getProfile(ProfileManager.java:52)

Wrote a small code to test Profile[] getProfile call in HostProfilesManager. I get the same exception. is viJava broken for HostProfiles?

Thanks
V

private void testHostProfiles() {
HostProfileManager hpm = si.getHostProfileManager();
Profile[] profiles = hpm.getProfile(); // this call throws the exception.
for (Profile p : profiles) {
System.out.println(“Profile “+ p);
}
}
/*
* Method from ProfileManager.java
public Profile[] getProfile()
{
return (Profile[]) getCurrentProperty(“profile”); // this is the call in ProfileManager causing the exception.
}
*/