Apache Camel integration proposal updates - First release

[Giacomo <gi...@tirasa.net>]

Hi all,

In these last days i tried to refactor what we said in the previous 
discussion [1] started by Hadrian. I tried to make the Provisioning 
Manager Camel independent, defining User and Role ProvisioningManager 
interfaces. In order to keep the actual functionality, i created two 
class, DefaultUserProvisioningManager and 
DefaultRoleProvisioningManager, that include the actual default 
implementation. The camel based functionality were moved in a new 
subpackage of the actual implementation, *.camel: it can be seen as a 
initial step of making the provisioning pluggable. Hadrian will help me 
in this part.

Besides this architectural points, i think that we are at a good stage 
(main functionalities are working), so i created a TAG called 
syncope-1.2.0-SNAPSHOT-Camelized, in order to give a first 'release' of 
the POC. However, there are still a lot of thing to fix: in example, 
Hadrian said me that there are Camel things that can be improved.

In the meanwhile, we are thinking about to 'propagate' these 
modification in the console part: it would be great, in the case we are 
using Camel,  to expose and define routes via Rest.

Any Suggestions?
Thanks for your time.

[1] 
http://syncope-dev.1063484.n5.nabble.com/Fwd-PROPOSAL-ProvisioningManager-refactoring-td5714798.html 


-- 
Giacomo Lamonaco

Tirasa - Open Source Excellence
http://www.tirasa.net/