Integrate Service Scaffolder in FraSCAti Studio

[mdutoo]

To be prepared by INRIA and OW, then done in codecamp together.

Current architecture : soap to rest proxy done as a binding.http (servlet), wsdl to html generator done as implementation.velocity exposed as binding.http (servlet). See wiki (NOT UP TO DATE) https://github.com/easysoa/EasySOA/wiki/Easysoa-light

Integrating it in FStudio means templatizing the Scaffolder .composite (including by adding user & app to the service URLs) to make a composite template out of it and putting its libs in FStudio. As much as possible can be put in another composite to reuse (by implementation.composite) in said template and the embedded scaffolder (if kept).

Other goals and challenges are :

• to share best practices (jquery, dhtmlx, velocity, backbone...) on web UI in FraSCAti (Studio), improve existing Scaffolder and Studio (ex. move HTML out of java classes...)
• to see how this integration can also make Service Scaffolder more useful, notably by allowing to edit the velocity template of the HTML UI and / or its generated HTML, and how to be win-win
• Further find best practices (for developing a FraSCAti Studio template, enriching FraSCAti...) & improve both

Architectural opportunities

• replace by implementation.widget the custom soap to rest proxy in the Service Scaffolder, by calling it from our WSDL2HTML UI template.
• move wsdl to html generator to a dedicated implementation, or to a dedicated case of implementation.velocity like ServletVelocityImplementation.java hacks (see Message API : store and reuse for replay & simulation #73 and Clean architecture for velocity-templatized services #107) to expose SOAP services out of velocity templates, TODO see discussion there.