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?
Regards.
[1]
https://github.com/apache/syncope/blob/master/ext/camel/provisioning-camel/src/main/java/org/apache/syncope/core/provisioning/camel/CamelUserProvisioningManager.java
[2]
https://github.com/apache/syncope/blob/master/ext/camel/provisioning-camel/src/main/java/org/apache/syncope/core/provisioning/camel/processor/UserCreateProcessor.java
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC,
CXF Committer, OpenJPA Committer, PonyMail PPMC
http://home.apache.org/~ilgrosso/
