syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò <>
Subject [DISCUSS] Improving Camel-based provisioning
Date Fri, 15 Jul 2016 16:16:16 GMT
Hi all,
as you know, Camel-based provisioning is one of the coolest features 
among the several cool features in 2.0.

The implementation is essentially done this way: each method in 
CamelUserProvisioningManager [1] (and similarly for groups and any 
objects) invokes some Camel route, then at the end of the route, some 
'processor' is invoked (as [2] for example, when user is created).

As you might see from [2] and all similar classes in that package, there 
is still some relevant logic implemented in Java, which might be moved 
back to the route definition, hence increasing the general benefits of 
the whole concept of Camel-based provisioning.

Do you also see this as an enhancement? Do you think it is possible / 
feasible to implement with limited effort?



Francesco Chicchiriccò

Tirasa - Open Source Excellence

Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC,
CXF Committer, OpenJPA Committer, PonyMail PPMC

View raw message