The design of the participant code in the TOSCA PoC should be re-examined, keeping in mind these comments captured from a review of the participant code:

I thought we will have a common "participant-client" library (similar to sdc distribution client) which will wrap all the communications to other tosca-controlloop components over dmaap, rest api etc. That way integrating a new participant will be pretty generic and quick. And participants are only responsible for consuming/publishing contents using the api's exposed by the client.

Should be similar to the Actor model, with a standard set of APIs, one for ingress and another for egress. Would also have common superclasses, like the HTTP & Topic classes in the Actor model, with common configuration properties/structures, depending on the type of superclass. Should also support pluggable components via a META-INF file.