easysoa/EasySOA — Issue #59: Scaling up FraSCAti proxies
Author: mdutoo
Created: 2011-10-13 17:57:29+00:00
State: open

For now, each proxy (scaffolder, monitoring) is instanciated once and calls proxied service using Apache HTTP Client. How to do this call in a more FraSCAti-like way ? Alternatives :

* keep proxies as singletons and, but add in FraSCAti the ability to call a web service the "message" way, i.e. using XML content rather than objects, kind of an outgoing binding.http with an HTTPMessage interface
* instantiate a new proxy "on demand" for each proxied service, which requires
* routing in front of FraSCAti (outside using connect or inside if possible using Camel or custom proxy) in order to redirect to different FraSCAti Services according to the actual target HTTP URL
* for non-SOAP HTTP ("RESTful") services, a non-SOAP HTTP client binding and interface, actually like the previous alternative
* (in addition to an instantiation manager)

Other topics :

* FraSCAti instantiation & deployment manager
* FraSCAti templatizing (abstract components, composition, includes, **propertizing**), FraSCAti templates composition manager
* Support of any service (any WSDL, with auth or not...) as client or proxy / mockup server - alternatives :
* multi runtime
* configuring CXF below FraSCAti
* anonymous bindings i.e. configuring CXF through FraSCAti