You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by Francesco Chicchiriccò <il...@apache.org> on 2013/12/06 10:02:44 UTC

Re: [Proposal] An Apache Camel Integratation Proposal

Hey Hadrian and Giacomo,
how things are proceeding? Are you facing some weird issues? Are you 
close to the target?
Please keep us informed about your progresses :-)

Regards.

On 21/11/2013 08:37, Francesco Chicchiriccò wrote:
> On 20/11/2013 20:12, Hadrian Zbarcea wrote:
>
>> I saw the proposal on user@camel and it sounds great. I see potential
>> fringe benefits for the Camel project as well and volunteer to help out.
>
> Great to hear!
> I think I've found you on GitHub: if you agree, I'd add you as 
> committer to https://github.com/Tirasa/SyncopeCamel
>
> I can provide some (more) guidance to Syncope internals, if needed.
>
> Summarizing: Giacomo, Hadrian (and anyone else interested) will be 
> building a PoC - based on referenced proposal - on the above mentioned 
> GitHub repository. This mailing list will be used for any related 
> discussion (if you agree, I will enable the mail notification from 
> GitHub to dev@).
> Once done, we will start discussing whether to a start a complete 
> implementation (somewhere in the official Syncope SVN) based on PoC 
> results.
>
> Do you (or anyone else here at dev@) see any problem with this working 
> model? I am proposing this way (instead of a bare dedicate branch on 
> SVN) mainly because Giacomo is not committer (for Hadrian, being an 
> ASF member, there would be no issue).
>
> WDYT (especially fellow PMC members)?
>
> Regards.
>
>> On 11/20/2013 11:25 AM, Francesco Chicchiriccò wrote:
>>> Hi all,
>>> in order to be able to freely experiment with this proposal, I've
>>> created an almost empty repository at GitHub
>>>
>>> https://github.com/Tirasa/SyncopeCamel
>>>
>>> where Giacomo will be soon push a simple overlay project, based on
>>> Syncope 1.2.0-SNAPSHOT.
>>>
>>> The idea is to override there some Syncope components (UserController,
>>> RoleController, ...) and introduce the ProvisioningManager - being 
>>> still
>>> able to successfully run the relevant integration tests.
>>>
>>> Once we've get a working PoC there, we could start discussing 
>>> whether to
>>> perform a full implementation here, and also the pmost suitable way to
>>> accept Giacomo's contribution.
>>>
>>> WDYT?
>>> Regards.
>>>
>>> On 20/11/2013 15:24, Giacomo Lamonaco wrote:
>>>
>>>> Thanks for your reply! I really appreciate your interest. I'm planning
>>>> to release a POC in the next months, before the end of February,
>>>> because i can work on it only two days for week.
>>>>
>>>> I will keep you updated in the next weeks.
>>>>
>>>> Best Regards.
>>>>
>>>> ----- Messaggio originale -----
>>>> Da: "Colm O hEigeartaigh" <co...@apache.org>
>>>> A: dev@syncope.apache.org
>>>> Inviato: Mercoledì, 20 novembre 2013 14:52:00
>>>> Oggetto: Re: [Proposal] An Apache Camel Integration Proposal
>>>>
>>>> It looks pretty cool! It's great to see the further integration of
>>>> Syncope with other Apache projects (e.g. CXF). What sort of time frame
>>>> do you envisage for this task + for what version of Syncope - 1.2/1.3?
>>>> Colm.
>>>>
>>>> On Wed, Nov 20, 2013 at 11:25 AM, giacomolm
>>>> <gi...@tirasa.net>wrote:
>>>>
>>>>> I forgot the most important part .. what do you think ?
>>>>>
>>>>>> giacomolm wrote
>>>>>>> Hi,
>>>>>>>
>>>>>>> Apache Syncope is a great solution for Identity Management. In 
>>>>>>> this month I analyzed some use cases that led me to reflect 
>>>>>>> about the flexibility of provisioning process to adapt to 
>>>>>>> various (and sometimes very cumbersome) deployment scenarios.
>>>>>>>
>>>>>>> The questions is: How well Syncope orchestrates the 
>>>>>>> provisioning? The
>>>>>>> problem is that Syncope lacks of a provisioning manager: this 
>>>>>>> component could allow an easy and fully customizable definition 
>>>>>>> of provisioning
>>>>>>> control logic.
>>>>>>>
>>>>>>> My proposal [1] consists in a redefinition of the (user and role)
>>>>>>> controller concept, through the Apache Camel framework. Why this
>>>>>>> framework? I think that Camel fits the need of easy control logic
>>>>>>> definition. Moreover Camel supports a wide range of external 
>>>>>>> components: it means that it can be easily integrated with 
>>>>>>> existing frameworks, like Activiti.
>>>>>>>
>>>>>>> [1] http://www.slideshare.net/giacomolm/camel-proposaltirasa

-- 
Francesco Chicchiriccò

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

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/