Re: [Engine-devel] oVirt UI Plugins: Update on current progress
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
- 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"
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]
[1] - will be supported by UI plugin infrastructure
[2] - not supported by UI plugin infrastructure
Vojtech
----- Original Message -----
From: "Itamar Heim" <iheim(a)redhat.com>
To: "Vojtech Szocs" <vszocs(a)redhat.com>
Cc: "engine-devel" <engine-devel(a)ovirt.org>, "Einav Cohen"
<ecohen(a)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).