easysoa/EasySOA — Issue #103: Integrate SOAPUI as dev test tool, link it to the SOA model
Author: mdutoo
Created: 2012-02-16 18:54:57+00:00
State: open
Labels: Open Wide

## Why

* showcases how EasySOA adds value to third-party tools / solutions, by bringing much-needed manageability to SOAPUI confs, by linking them to the EasySOA known SOA model & services.
* more comprehensive & developer-oriented test tool (than scaffolder),
* well-known so will help buzz but also introducing (java) developers to EasySOA and making them comfortable here
* a prototype of functional integration with SOAPUI had been planned to see how far to go in such directions
* allows to address : using service use portal, where to store edited confs (like scaffolder), external tool integration (like Talend, fstudio)

## TODO

* for an env, allow user to generate soapui conf templated by webengine, by default containing definitions (WSDLs) of all services with default request samples, and if possible default service mocks
* study how to make it as easy as possible to use soapui on it : start an existing soapui when downloading it, or even embed it (ask talend how they did it).

## LATER

* study where to store user-edited confs (Nuxeo ? fs ? git ??) and how to refer to it in the model (soapui conf as appimpl / module ??). See also vs for other external tools (sca import and its different uses : design, runtime ; scaffolder : file system with exchangestore referenced in the model ; fstudio ; talend etc.)
* when storing / referencing them in the model, parse it. Apply the discovery mapper algorithm to each service url in order to find to which service in the model it refers to and link it to it (similar to SCA import, will probably look like a big application providing and consuming a lot of services)
* make it possible to fork / "transition" soapui confs between envs !
* study whether mapping it to applications smaller / closer to the "actual" one is feasible / better for understanding & representation. Like splitting soapui confs in several mock client and server appimpls ? Or even having "tridimensional" or "half transparent" models with said big application's component underneath as single implementation of a lot of upper "business" components, with easy browsing using one or the other ??