easysoa/EasySOA — Issue #58: EasySOA Light - Further handle complex service types
Author: mdutoo
Created: 2011-10-13 17:36:46+00:00
State: open

Why ? Now the limit is the WSDL to HTML form generator (be it based on XSL or velocity+WSDL Java model). It supports simple params (primitive types) OK (ex. paf, travel), but not more complex types. This issue is more complex technically, but we even more need to think about how to make this feature useful : merely having a tree of forms to input complex types won't help the business user, and the dev user probably prefers raw XML. Here are alternatives to make it useful to the business user :

* "templates" : an idea is to only require him to input the few fields that really interest him, and "templatize" the remaining xml (got from a previously recorded exchange, or if none from the WSDL as now). This transformation could be designed either in an online interactive "exchange templatizer", in an outside Talend Studio...
* at the other end of the spectrum, mashups / Light development : develop an EasySOA Light app with a custom UI and custom code (script) calling services. These service calls could be helped by various tools : FraSCAti binding.html or REST to SOAP proxy, SPoRE client api...
* in a more framed / patterned process, by following a "divide and conquer" approach : develop "simpler" EasySOA Light services, each exposing only a part of the main service it calls, and composing them all again in a single EasySOA Light UI
* use all of those : templates, simpler Light services, Light UI
* NB. This feature, along with others, have to be thought about in the whole "SOA on rails" functional perimeter, and among the kind of proxies we're interested for INRIA's FraSCAti proxy factory.