Put advanced binding configuration (CXF, Jetty) more in composites

[mdutoo]

("anonymous bindings")

rather than in a global config file (ex. cxf-config.xml , which could do it but then would be a mirror of .composite files), to allow different configuration on each service.

long term issue

Example : configure the timeout or the HTTP proxy to be used by a given binding.ws on client side, or much farther configure a specific interceptor chain.

Example of what is not possible today (?) : start two implementations of the same service on different URLs, and

• let one use a proxy and the other not,
• or let one use a monitoring proxy that will extract technical or business headers, and the other one a monitoring proxy that will extract other headers.

Solution ideas :

• binding configuration can be provided in XML in the composite using several SCA properties, or a single appropriately named JAXB property. It could also be under the binding.xxx XML element, but this is less flexible because only INRIA can define its schema.
• binding runtime (ex. CXF, Jetty) can be configured dynamically in Fractal BF, or through generation of cxf config file
• workaround : embedding (using SCA configuration) our own HTTP proxy technology (ex. HTTP monitoring proxy) in our FraSCAti clients (ex. Light proxies), but that makes FraSCAti less useful

20120615 update on requirements

• extract HTTP info ex. headers : for monitoring (_), discovery (client & server url), event (idem) ; maybe fuse, also for security (ex. BasicAuth OK) & caching (timestamp). Further access the full HTTP message : to deploy our HTTP Miner library which records HTTP exchange, for now is a Servlet deployed on Jetty (__). _OK* by writing custom CXF Interceptors or JAXWS Handlers for all (HandlerManager) or each (Monitoring, Discovering, Eventing, Recording handlers) of these purposes.
• configure CXF :
  • timeout OK,
  • proxy OK,
  • add CXF interceptors or JAXWS handlers OK ex. security, monitoring (see above)

() see a list of monitored fields : https://github.com/easysoa/EasySOA/wiki/Final-monitoring-design/ (*) allows to replay request with assertions on response, replay templatized exchanges, generate simulations the same way : http://www.easysoa.org/2012/05/easysoa-http-mining-feature/

Some of these Proxy ideas are also listed at https://github.com/easysoa/EasySOA/wiki/Easysoa-proxy-use-cases

20120822 how it will be used

• fuse : no changes for now (later business code could be improved & an admin service & ui added to allow managing state & "unfusing" as well as setting limits per probe and / or user)
• setting up proxy of FraSCAti service...
  • client : do it using ProxyServerIntent it for 1. samples, 2. FraSCAti StudioTODO universal proxy or not ?
  • server : cxf.apache.org/docs/standalone-http-transport.html
• security :
  • BasicAuth is possible using BasicAuthorizationPolicyIntent (maybe add a sample). MERLE: see http://websvn.ow2.org/filedetails.php?repname=frascati&path=%2Ftrunk%2Ffrascati%2Fintents%2Fapache-cxf%2Fsrc%2Ftest%2Fresources%2FMyAuthorization.composite
  • CXF security interceptors (such as UsernameToken, JAAS or even authorization forwarding) can be reused by writing other InterceptorIntents. Beyond, custom CXF interceptors (or JAXWS handlers) could be written
  • HTTPS (SSL / TLS) auth using CXF can be setup on client side by writing another ConduitIntent that configures the conduit like said here
  • TODO INRIA HTTPS (SSL / TLS) auth using CXF can be setup on server side by configuring CXF's JettyHTTPServerEngine's TLSServerParameters like said here in a new BindingIntent (see what CXF configuration is accessible there). Note that it does not cover other FraSCAti servers such as velocity.
• TODO INRIA receive timeout, cache control : can be set by writing new BindingIntents that configure HTTPServerPolicy on CXF ServerImpl's AbstractHTTPDestination like said here.
• TODO INRIA implementation.velocity : in the same spirit, could be configured (ex. add a (MessageHandlerManager)HttpFilter) by a new (MessageHandlerManager)BindingIntent that applies on Jetty server.
• monitoring :
  • First note that how handlers are deployed (HandlerManager in HttpFilter or HttpProxy vs FraSCAti-configured CXF interceptors), how they are activated (or further configured, ex. partial only handling such as only monitor headers...) are distinct things.
  • when using CXF interceptors (or JAXWS handlers), CXF interceptor loop plays the role of HandlerManager
  • In one probe per service mode, each service has its own FraSCAti-defined handler instances which can be configured in Light UI (and might get in FStudio a setup different from default's, for CXF or HttpProxy)
  • in universal proxy mode, it's more of a "all or nothing" / "create a dedicate probe if it's not enough" (though we might use Conditions for each handler, or have a front service router relying on EasySOA knowledge of services to instanciate and route between a HandlerManager per service, but hot reconfiguration of dedicated probes would be better)
  • add MessageHandler.handleBefore() throw Exception to allow to : fuse, monitor date before...

FAQ :

• Got an exception with the following message : not a proxy client => the intent is not plugged on a client binding but on a server binding. A client binding is generally placed in a reference tag.

[philippemerle]

Added a prototype to configure intents on SCA bindings. Have a look at http://websvn.ow2.org/listing.php?repname=frascati&path=%2Ftrunk%2Ffrascati%2Fintents%2Fapache-cxf%2F

This provides a first implementation of SCA intents for Apache-CXF-based SCA bindings. Five intents are provided:

• Logging: set up CXF logging interceptors on SCA bindings.
• ConnectionTimeout: set up connection timeout on SCA client bindings.
• ReceiveTimeout: set up receive timeout on SCA client bindings.
• Authorization: set up authorization policy on SCA client bindings.
• ProxyServer: set up proxy server useb by SCA client bindings.
• as well as a TraceHandler showing how to set up JAW-WS Handler on Web Service SCA bindings.

[mdutoo]

Nice, this should do the trick, we'll try at least using ProxyServer and write our own Monitoring intent once 0.4 is out.