Setting up XBaya WebUI

[Supun Nakandala <su...@gmail.com>]

Hi all,

I cloned the XBaya WebUI code from [1] and managed to build the web app.

But when I run the application (using grunt server command) I can see I get
two errors in the Chrome console as shown in attached err_0.png image. One
error is related to "undefined require" and other one is related to a
failure of loading a resource

When I try to connect to the registry I get another error in the Chrome
console as shown in err_1.png and err_2.png. That error is due to "not
allowed access". But using the same registry URL I can connect to the
registry using XBaya without any issues.

I tried to solve this issue by my self for some time now. But I was
unsuccessful. I would appreciate your help to fix these issues.

Regards
Supun Nakandala

[1] - https://svn.apache.org/repos/asf/airavata/sandbox/gsoc2013/

Re: Setting up XBaya WebUI

[Shameera Rathnayaka <sh...@gmail.com>]

Hi Supun,

We implemented separate JS client API[1] which can be used to call airavata
registry and web UI project suppose to use that client to do registry
calls. But unfortunately we have an issue when we try to integrate the JS
client with web UI project which has written in Angular.js. Still we are
trying to connect the dots. Here the root cause is,  get the angular MVC
design works, we need to use $http method comes with Angular.js to do rest
calls and we can't use JS Client API for that. For the sake of complete the
web UI project what we thought was, implement that $http functions and it
is not finish yet. As this is tightly couple with Anjular.js we can't
provide generic JS client API with this way. Sanchit and Subho can explain
this with more details.

[1]
https://cwiki.apache.org/confluence/display/AIRAVATA/JavaScript+Regsitry+Client

Thanks,
Shameera.


On Wed, Mar 5, 2014 at 9:14 AM, Saminda Wijeratne <sa...@gmail.com>wrote:

> Perhaps previous GSoC students engaged in this project could shed more
> light on this. However I'd urge to use the Airavata latest release at the
> time of GSoC 2013 completion. Also try writing a small web page containig
> the js scripts which connects to the registry.
>
>
> On Tue, Mar 4, 2014 at 1:34 PM, Supun Nakandala <supun.nakandala@gmail.com
> > wrote:
>
>> Hi all,
>>
>> I cloned the XBaya WebUI code from [1] and managed to build the web app.
>>
>> But when I run the application (using grunt server command) I can see I
>> get two errors in the Chrome console as shown in attached err_0.png image.
>> One error is related to "undefined require" and other one is related to a
>> failure of loading a resource
>>
>> When I try to connect to the registry I get another error in the Chrome
>> console as shown in err_1.png and err_2.png. That error is due to "not
>> allowed access". But using the same registry URL I can connect to the
>> registry using XBaya without any issues.
>>
>> I tried to solve this issue by my self for some time now. But I was
>> unsuccessful. I would appreciate your help to fix these issues.
>>
>> Regards
>> Supun Nakandala
>>
>> [1] - https://svn.apache.org/repos/asf/airavata/sandbox/gsoc2013/
>>
>
>


-- 
Best Regards,
Shameera Rathnayaka.

email: shameera AT apache.org , shameerainfo AT gmail.com
Blog : http://shameerarathnayaka.blogspot.com/

Re: Setting up XBaya WebUI

[Saminda Wijeratne <sa...@gmail.com>]

Perhaps previous GSoC students engaged in this project could shed more
light on this. However I'd urge to use the Airavata latest release at the
time of GSoC 2013 completion. Also try writing a small web page containig
the js scripts which connects to the registry.


On Tue, Mar 4, 2014 at 1:34 PM, Supun Nakandala
<su...@gmail.com>wrote:

> Hi all,
>
> I cloned the XBaya WebUI code from [1] and managed to build the web app.
>
> But when I run the application (using grunt server command) I can see I
> get two errors in the Chrome console as shown in attached err_0.png image.
> One error is related to "undefined require" and other one is related to a
> failure of loading a resource
>
> When I try to connect to the registry I get another error in the Chrome
> console as shown in err_1.png and err_2.png. That error is due to "not
> allowed access". But using the same registry URL I can connect to the
> registry using XBaya without any issues.
>
> I tried to solve this issue by my self for some time now. But I was
> unsuccessful. I would appreciate your help to fix these issues.
>
> Regards
> Supun Nakandala
>
> [1] - https://svn.apache.org/repos/asf/airavata/sandbox/gsoc2013/
>