3rdparty Framework Integration

Sept 22, 2017

1 Prio 2 Apache CXF SOAP Client
2 Later Apache CXF SOAP Server
3 Prio 2 REST Client

Prio 1 Apache HTTP Client

done: http://caravan.wcm.io/commons/httpclient/ and http://caravan.wcm.io/commons/httpasyncclient/

Factory configuration for HTTP client settings based on white- and blacklists of hosts
Configuration of connect and response timeouts and maximum of connections
Configuration of proxy servers
Configuration of basic authentication
Configuration of SSL trust stores
Configuration of mutual authentication based on SSL client certs
Re-use/Caching of HTTP client instances
Support HTTP client initializer for special configuration

Prio 2 Apache CXF SOAP Client

done: http://caravan.wcm.io/jaxws/consumer/ and http://caravan.wcm.io/jaxws/consumer-httpclient/

Same HTTP connection settings as supported for Apache HTTP clients
Re-use/Caching of CXF client instances
Support CXF client initializer for special configuration
Configuration of schema validation (default: off, accept unknown elements)
Thread OSGi-related classloader problems
Evaluate the SOAP service infrastructure that is included in CQ6 already (but that is not based on CXF?)

Later Apache CXF SOAP Server

done: http://caravan.wcm.io/jaxws/publisher/

Support implementing SOAP servers within CQ

Prio 2 REST Client

open, partially done (but not so lightweight) with http://caravan.wcm.io/io/ and http://caravan.wcm.io/pipeline/ - not well documented

Infrastructure for implementing lightweight clients for REST interfaces
Based on Apache HTTP Client
With our without support for WADL
To be defined which / if a 3rdparty Framework like Apache CXF is used here as well