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 <[email protected]> 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 <[email protected]> > wrote: > > > > On Wed, Sep 18, 2013 at 10:55 AM, Chathuri Wimalasena <[email protected]> > 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 > >
