Mailing-List: contact dev-help@syncope.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@syncope.apache.org
To: dev@syncope.apache.org
From: =?UTF-8?Q?Francesco_Chicchiricc=c3=b2?= <ilgrosso@apache.org>
Subject: [DISCUSS] Improving Camel-based provisioning
Message-ID: <9e7aeae9-7438-1634-520c-7cac27fc4d7e@apache.org>
Date: Fri, 15 Jul 2016 18:16:16 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 15 Jul 2016 16:16:23 -0000

Hi all,
as you know, Camel-based provisioning is one of the coolest features=20
among the several cool features in 2.0.

The implementation is essentially done this way: each method in=20
CamelUserProvisioningManager [1] (and similarly for groups and any=20
objects) invokes some Camel route, then at the end of the route, some=20
'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=20
back to the route definition, hence increasing the general benefits of=20
the whole concept of Camel-based provisioning.

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

Regards.

[1]=20
https://github.com/apache/syncope/blob/master/ext/camel/provisioning-came=
l/src/main/java/org/apache/syncope/core/provisioning/camel/CamelUserProvi=
sioningManager.java
[2]=20
https://github.com/apache/syncope/blob/master/ext/camel/provisioning-came=
l/src/main/java/org/apache/syncope/core/provisioning/camel/processor/User=
CreateProcessor.java

--=20
Francesco Chicchiricc=C3=B2

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/