In your eclipse project, what version of vim25.jar does it depend
> >>> on? 5.1 or 4.1? If you are using 5.1 version, then you cannot use those
> >>> AppUtil class anymore.
> >>>
> >>> Thanks
> >>> -min
> >>>
t;>> In your eclipse project, what version of vim25.jar does it depend
>>> on? 5.1 or 4.1? If you are using 5.1 version, then you cannot use those
>>> AppUtil class anymore.
>>>
>>> Thanks
>>> -min
>>> ___
>> -min
>>
>> From: Mike Tutkowski [mike.tutkow...@solidfire.com]
>> Sent: Monday, March 18, 2013 9:03 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: VMware and RuntimeFault class
>>
>> Here i
ss anymore.
>
> Thanks
> -min
>
> From: Mike Tutkowski [mike.tutkow...@solidfire.com]
> Sent: Monday, March 18, 2013 9:03 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: VMware and RuntimeFault class
>
> H
@incubator.apache.org
Subject: Re: VMware and RuntimeFault class
Here is a screen shot of what I'm seeing:
http://snag.gy/RQyxY.jpg
In the getProperties method, Eclipse is saying I have an unhandled
exception. However, that method throws Throwable, so I should be good to
go.
If I look at the refer
Here is a screen shot of what I'm seeing:
http://snag.gy/RQyxY.jpg
In the getProperties method, Eclipse is saying I have an unhandled
exception. However, that method throws Throwable, so I should be good to
go.
If I look at the referenced RuntimeFault class, it does not extend
Throwable (either
Here's a good example:
public abstract interface com.vmware.vim.VimPortType extends java.rmi.Remote
{
// Method descriptor #107
(Lcom/vmware/vim/ManagedObjectReference;Ljava/lang/String;)Lcom/vmware/vim/ManagedObjectReference;
public abstract com.vmware.vim.ManagedObjectReference
findByInventor
It looks like there are two RuntimeFault classes (one of which extends
Throwable indirectly).
com.vmware.vim.RuntimeFault is not a Throwable.
com.vmware.vim25.RuntimeFault is a Throwable.
The funny part is the sample code I have is not using com.vmware.vim25 at
all, yet it uses RuntimeFault as a
This person had the same problem, but I don't really understand the
solution:
http://communities.vmware.com/message/1896784
On Mon, Mar 18, 2013 at 7:12 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> Hi Min,
>
> I think this is VI Java...I'm just learning about that (haven't used i
Hi Min,
I think this is VI Java...I'm just learning about that (haven't used it
before).
I guess maybe I don't understand what VI Java is. Is it not expected to
conform to normal Java compile rules (like any exception you throw must be
a Throwable)?
Thanks for clarifying this for me!
On Mon,
Hi guys,
I appreciate the comments - thanks!
I agree...just because it has Runtime in the name doesn't mean anything.
My problem is that the object they are throwing is from a class that does
not derive from Throwable at all...not only does it not derive from
RuntimeException or Exception, it ju
VMware API is web-service based, how a web service fault class is mapped
to a java class is determined by the underlying web-service tool.
In vSphere 4.0/4.1 SDK, it uses Axis 1.4, all web server fault class is
derived from org.apache.axis.AxisFault which in turn derives from java
Exception class.
Which sample code are you looking at? I am looking at sample files coming
with 5.1 vim25.jar, they always throw RuntimeFaultFaultMsg. Can you tell
me the java file name you are looking at? Maybe you are using VI java, not
VMware SDK jar?
Thanks
-min
On 3/18/13 4:06 PM, "Mike Tutkowski" wrote:
>
Here is some of the problematic sample code:
ObjectContent[] ocs = service.retrieveProperties(
content.getPropertyCollector(),
new PropertyFilterSpec[] {pfSpec});
It claims to throw a RuntimeFault exception. However, when I look at the
API docs for RuntimeFaul
In Vmware 5.1 SDK, RuntimeFaultFaultMsg is the exception class for
RuntimeFault. RuntimeFault itself is not extended from Throwable.
Thanks
-min
On 3/18/13 3:39 PM, "Mike Tutkowski" wrote:
>Hi,
>
>I've been playing around with VMware API commands to create a datastore.
>
>In sample code I've fo
Does CloudStack currently create datastores via vCenter or is that
something the user has to set up ahead of time (like doing the PreSetup
option with XenServer)?
On Mon, Mar 18, 2013 at 4:56 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> It looks like this is part of the VI Java AP
It looks like this is part of the VI Java API. It is possible this code,
while looking a lot like Java (and having the word "Java" in its name), is
not actually Java code?
On Mon, Mar 18, 2013 at 4:39 PM, Mike Tutkowski <
mike.tutkow...@solidfire.com> wrote:
> Hi,
>
> I've been playing around w
17 matches
Mail list logo
