[Engine-devel] oVirt UI Plugins: Update on current progress

[Itamar Heim]

On 07/23/2012 12:40 PM, Vojtech Szocs wrote:
>> this implies server side code running on the engine,
>
> Actually, yes and no :) let me explain:
>
> - UI plugins developed in GWT need some context (plugin web application deployed next to engine.ear) from which their code will be served

it is not supposed to be next to engine.jar, it is supposed to be 
somewhere else entirely, served to clients like any static content via a 
servelt.

> - UI plugin web applications can contain only static resources (HTML + generated JavaScript) -> answer is "NO"
> - UI plugin web applications can also contain server-side code (e.g. for GWT RPC) -> answer is "YES"

that's not the scope we discussed so far.
we discussed a 'static' plugin, which can use an external service or the 
REST API.

>
>> which has additional implications on compatibility vs. ui plugins as discussed
>
> I don't think we need to worry about this :)
>
> If a GWT UI plugin web application needs to use Engine functionality, it can:
>
> - use REST API from within UI plugin (JavaScript) code [1]
> - use REST API from within its server-side (Java) code [2]

again, if we want to discuss an approach to making ui plugins which need 
server side cooperation not in a separate container of their own choice, 
different server, etc. - we can, but lets separate the discussion on the 
two.

>
> [1] - will be supported by UI plugin infrastructure
> [2] - not supported by UI plugin infrastructure
>
> Vojtech
>
>
> ----- Original Message -----
> From: "Itamar Heim" <iheim at redhat.com>
> To: "Vojtech Szocs" <vszocs at redhat.com>
> Cc: "engine-devel" <engine-devel at ovirt.org>, "Einav Cohen" <ecohen at redhat.com>
> Sent: Monday, July 23, 2012 9:10:07 AM
> Subject: Re: oVirt UI Plugins: Update on current progress
>
> On 07/20/2012 11:37 PM, Vojtech Szocs wrote:
>> Last but not least, writing plugins in Google Web Toolkit (GWT) should
>> be as easy as providing your own plugin source page. Just deploy your
>> GWT plugin application on JBoss AS (next to engine.ear), and point to
>> GWT plugin application host page.
>
> this implies server side code running on the engine, which has
> additional implications on compatibility vs. ui plugins as discussed so
> far which would be java script
> (I'm not against using GWT for them if the resulting java script can be
> packaged for use as a UI plugin, but sever side code i prefer to be
> isolated from engine until we'll define engine plugins).
>
>