You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by Chathuri Wimalasena <ka...@gmail.com> on 2013/09/18 16:55:49 UTC

XBaya initialization fails with NPE when it is instantiated from a client code

Hi Devs,

When we open xbaya from a client code programmatically, we do not have a
way to set the airavata api object. When we instantiate a new xbaya
instance, we just pass set of parameters such as registry url, registry
user, password, gfac url etc. During initialization, we assumed that the
airavata-api is already set. We never do a null check or anything like that
before accessing any method from airavata-api. As a result, XBaya
initialization fails.

This bug [1] is in 0.8 release and it is still in trunk as well.

Regards,
Chathuri

[1] https://issues.apache.org/jira/browse/AIRAVATA-920

Re: XBaya initialization fails with NPE when it is instantiated from a client code

Posted by Suresh Marru <sm...@apache.org>.
Just calling the XBaya main class directly (with required arguments) instead of calling it from JNLP or a shell script.

Suresh

On Sep 18, 2013, at 1:54 PM, Chathuri Wimalasena <ka...@gmail.com> wrote:

> Hi Amila, 
> 
> It is something like this. From paramboroo client, we are popping up xbaya window for monitoring. In that case, what we do is instantiate the XBaya object with necessary parameters that is needed for XBaya. That is what I meant by "opening xbaya from a client code programmatically".
> 
> Regards,
> Chathuri
> 
> 
> On Wed, Sep 18, 2013 at 1:45 PM, Amila Jayasekara <th...@gmail.com> wrote:
> 
> 
> 
> On Wed, Sep 18, 2013 at 10:55 AM, Chathuri Wimalasena <ka...@gmail.com> wrote:
> Hi Devs, 
> 
> When we open xbaya from a client code programmatically
> 
> What do you mean by "opening xbaya from a client code programmatically" ?
> 
> Thanks
> Amila
>  
> , we do not have a way to set the airavata api object. When we instantiate a new xbaya instance, we just pass set of parameters such as registry url, registry user, password, gfac url etc. During initialization, we assumed that the airavata-api is already set. We never do a null check or anything like that before accessing any method from airavata-api. As a result, XBaya initialization fails.   
> 
> This bug [1] is in 0.8 release and it is still in trunk as well.   
> 
> Regards,
> Chathuri
> 
> [1] https://issues.apache.org/jira/browse/AIRAVATA-920
> 
>

Re: XBaya initialization fails with NPE when it is instantiated from a client code

Posted by Chathuri Wimalasena <ka...@gmail.com>.
Hi Amila,

It is something like this. From paramboroo client, we are popping up xbaya
window for monitoring. In that case, what we do is instantiate the XBaya
object with necessary parameters that is needed for XBaya. That is what I
meant by "opening xbaya from a client code programmatically".

Regards,
Chathuri


On Wed, Sep 18, 2013 at 1:45 PM, Amila Jayasekara
<th...@gmail.com>wrote:

>
>
>
> On Wed, Sep 18, 2013 at 10:55 AM, Chathuri Wimalasena <
> kamalasini@gmail.com> wrote:
>
>> Hi Devs,
>>
>> When we open xbaya from a client code programmatically
>>
>
> What do you mean by "opening xbaya from a client code programmatically" ?
>
> Thanks
> Amila
>
>
>> , we do not have a way to set the airavata api object. When we
>> instantiate a new xbaya instance, we just pass set of parameters such as
>> registry url, registry user, password, gfac url etc. During initialization,
>> we assumed that the airavata-api is already set. We never do a null check
>> or anything like that before accessing any method from airavata-api. As a
>> result, XBaya initialization fails.
>>
>> This bug [1] is in 0.8 release and it is still in trunk as well.
>>
>> Regards,
>> Chathuri
>>
>> [1] https://issues.apache.org/jira/browse/AIRAVATA-920
>>
>
>

Re: XBaya initialization fails with NPE when it is instantiated from a client code

Posted by Amila Jayasekara <th...@gmail.com>.
On Wed, Sep 18, 2013 at 10:55 AM, Chathuri Wimalasena
<ka...@gmail.com>wrote:

> Hi Devs,
>
> When we open xbaya from a client code programmatically
>

What do you mean by "opening xbaya from a client code programmatically" ?

Thanks
Amila


> , we do not have a way to set the airavata api object. When we instantiate
> a new xbaya instance, we just pass set of parameters such as registry url,
> registry user, password, gfac url etc. During initialization, we assumed
> that the airavata-api is already set. We never do a null check or anything
> like that before accessing any method from airavata-api. As a result, XBaya
> initialization fails.
>
> This bug [1] is in 0.8 release and it is still in trunk as well.
>
> Regards,
> Chathuri
>
> [1] https://issues.apache.org/jira/browse/AIRAVATA-920
>