EasySOA-registry Web FrontEnd

[tiry]

There seen to be currently several WebUI on top of EasySOA :

• Nuxeo JSF UI (mainly back office from my understanding)
• Nuxeo WebEngine (mainly Rest since the only template is for now a static html)
• node.js
• backbone.js

I undertsand the idea of testing several technos.

I also undertsand the need for choosing the right technology for given purpose.

But I will need to know in a near future what is chosen as the main Front End Web UI :

• because if we integrate Documentation items on services we will need wiki markup support
• because it's not very efficient to have a rendeing server talking via http to a data server (even if this is SOA oriented :) )

If needed, we can integrate backbone.js support in WebEngine (like we did for GWT for example).

Anyway we must define what we want to build on ...

[mdutoo]

My first idea was that Nuxeo JSF UI is good for documentation, so can be used for SOA documentation purposes, and what's done there may also be of interest to Nuxeo.

We're going to decide on other UIs according to the functional perimeter.

About efficiency of front UI doing HTTP to data backend : we have to talk about that :) if only precisely because it's SOA.

[tiry]

I take the example of Platform Explorer Addon that is basically very much what EasySOA Core is, at least from a documentation point of view : a Way to capture and persist the definition of a versionned set of components and services, attach documentation to them and provide browsing / searching.

Currently we have mainly 3 access types :

• API access via adapters
• Browsing and Documentation Access via WebEngine (Freemarker, Html, JQuery)
• Management via JSF Web UI

I don't see why this small EasySOA4Nuxeo could not be shared with EasySOA Core. I can adapt the Explorer, but I definitly would like to make the 2 projects converge in the same direction.

=> I need to discuss about what we all want for UI :)