[jira] [Resolved] (SYNCOPE-1044) By editing the provisioning rules, modal footer is not disabled

2017-03-13 Thread fabio martelli (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

fabio martelli resolved SYNCOPE-1044.
-
Resolution: Fixed

> By editing the provisioning rules, modal footer is not disabled
> ---
>
> Key: SYNCOPE-1044
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1044
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.2
>Reporter: fabio martelli
>Assignee: fabio martelli
> Fix For: 2.0.3, 2.1.0
>
>
> By editing the provisioning rules, modal footer is not disabled.
> Clicking on finish or cancel it is.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SYNCOPE-1044) By editing the provisioning rules, modal footer is not disabled

2017-03-13 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907707#comment-15907707
 ] 

ASF subversion and git services commented on SYNCOPE-1044:
--

Commit 032d70e5d76718979f6f0cf962e3e80b2534345d in syncope's branch 
refs/heads/2_0_X from [~fmartelli]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=032d70e ]

[SYNCOPE-1044] fixes by remving a double send event


> By editing the provisioning rules, modal footer is not disabled
> ---
>
> Key: SYNCOPE-1044
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1044
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.2
>Reporter: fabio martelli
>Assignee: fabio martelli
> Fix For: 2.0.3, 2.1.0
>
>
> By editing the provisioning rules, modal footer is not disabled.
> Clicking on finish or cancel it is.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (SYNCOPE-1044) By editing the provisioning rules, modal footer is not disabled

2017-03-13 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15907708#comment-15907708
 ] 

ASF subversion and git services commented on SYNCOPE-1044:
--

Commit a0ffad75eeb166590f05f2d80d043c56b620023c in syncope's branch 
refs/heads/master from [~fmartelli]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=a0ffad7 ]

[SYNCOPE-1044] fixes by remving a double send event


> By editing the provisioning rules, modal footer is not disabled
> ---
>
> Key: SYNCOPE-1044
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1044
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 2.0.2
>Reporter: fabio martelli
>Assignee: fabio martelli
> Fix For: 2.0.3, 2.1.0
>
>
> By editing the provisioning rules, modal footer is not disabled.
> Clicking on finish or cancel it is.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [DISCUSS] Replace Activiti with Flowable?

2017-03-13 Thread Colm O hEigeartaigh 
Also +1 from me.

Colm.

On Tue, Mar 7, 2017 at 8:24 AM, Fabio Martelli 
wrote:

> Hi Francesco, sorry for the late reply.
> Flowable sounds really interesting. I agree on the pair of steps you
> proposed below.
>
> +1 to move Apache Syncope in this direction.
>
> Best regards,
> F.
>
> Il 21/02/2017 20:31, Francesco Chicchiriccò ha scritto:
>
>> Hi all,
>> I have been recently made aware that many of the original developers of
>> Activiti (including the team leader Tijs Rademakers) started a new fork,
>> Flowable [1].
>> The detailed reasons for forking can be read from [2] but, besides these,
>> I think we need to decide whether to stick with Activiti as our predefined
>> workflow engine, or if instead it is be the case to move to Flowable.
>>
>> It seems that one of the main reasons behind the fork is the fact that
>> the original team wasn't able to cut out the new 6.0.0 release (which is
>> being worked since long time); the new team has recently published 6.0.0
>> [3] and also a maintenance 5.22.0 [4] (which is the version we are
>> currently using, but from Activiti).
>>
>> Flowable 6 looks really interesting, especially for the cleaning and the
>> refactoring they made - which also solved the issue raised a while ago in
>> [5] about the Activiti Modeler license: it seems that the new Flowable UI
>> Modeler is completely AL 2.0 compliant; moreover, they introduced some
>> interesting support for multi-tenancy [6] which we can leverage.
>>
>> I would propose to:
>>
>> 1. open an issue to make the 2.1 series (e.g. the current master
>>branch) work with Flowable 6, replacing Activiti
>> 2. open an issue to provide an additional module for the 2.0 series
>>(e.g. the current 2_0_X branch), named workflow-flowable, mostly a
>>clone of workflow-activiti [7] but with different dependencies;
>>workflow-activiti will remain the default choice, but people could
>>switch to Flowable on their own deployments if they will
>>
>> WDYT?
>> Regards.
>>
>> [1] http://www.flowable.org/
>> [2] http://www.flowable.org/blog/2016/10/12/flowable-and-activiti.html
>> [3] http://www.flowable.org/blog/2017/02/15/flowable-6.0.0-release.html
>> [4] http://www.flowable.org/blog/2016/10/13/flowable-5.22.0-release.html
>> [5] https://issues.apache.org/jira/browse/SYNCOPE-439?focusedCom
>> mentId=13829912=com.atlassian.jira.plugin.system.
>> issuetabpanels:comment-tabpanel#comment-13829912
>> [6] http://forum.flowable.org/t/support-for-additional-multi-ten
>> ancy-models/175
>> [7] https://github.com/apache/syncope/tree/2_0_X/core/workflow-activiti
>>
>>
>
> --
> Fabio Martelli
> https://it.linkedin.com/pub/fabio-martelli/1/974/a44
> http://blog.tirasa.net/author/fabio/index.html
>
> Tirasa - Open Source Excellence
> http://www.tirasa.net/
>
> Apache Syncope PMC
> http://people.apache.org/~fmartelli/
>
>


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Re: GSOC contribution for SYNCOPE-1018 Social registration for Enduser UI

2017-03-13 Thread govinda Malavipathirana 
Hi'
I successfully builded the project and read the source code as well. Then I
started the development on end user ui. I want to know about how is the
proposal phase happening. Do the apache has some specific template(for
proposal) for it.
Best regards,
Govinda.

On Saturday, March 4, 2017, Andrea Patricelli 
wrote:

> No. Syncope is maven project.
> You should not have the timeout error shown in the first email. If you
> skip tests with skipTests profile maven does not execute such tests. Please
> could you attach the command that you are running and the timeout error
> that you are getting?
>
>
> Il giorno 4 mar 2017, 06:29, alle ore 06:29, govinda Malavipathirana <
> mp.govi...@gmail.com > ha scritto:
> >Hi'
> >I tried so many solutions like including above solution, building
> >without
> >testing... But I'm still out of luck. Time out problem is still there.
> >So I
> >thought I have 2 different options
> >1. Choose different build tool
> >2. Move for new machine.
> >I would rather like first option. So are there any build tool that
> >better
> >for syncope?
> >Sincerely,
> >Govinda.
> >
> >On Friday, March 3, 2017, Andrea Patricelli
> >>
> >wrote:
> >
> >> Hi Govinda,
> >>
> >> Maybe you have performace issues on your machine. Some tests could
> >fail
> >> due to HW performance issues, in fact the error is a timeout. Try to
> >run
> >> with mvn -T1C -Pall,skipTests to build the whole project.
> >>
> >> HTH,
> >> Andrea
> >>
> >> Il 03/03/2017 09:39, govinda Malavipathirana ha scritto:
> >>
> >>> Hi'
> >>> I have tried to build the syncope after the cloning using " mvn
> >clean
> >>> install" then it raise an error in test phase. It looks like this...
> >>> ---
> >>>   T E S T S
> >>> ---
> >>> Running org.apache.syncope.fit.cli.CLIITCase
> >>> Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> >74.142 sec
> >>> - in org.apache.syncope.fit.cli.CLIITCase
> >>> Running org.apache.syncope.fit.console.AjaxBrowseITCase
> >>> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> >20.808 sec
> >>> - in org.apache.syncope.fit.console.AjaxBrowseITCase
> >>> Running org.apache.syncope.fit.console.AjaxPalettePanelITCase
> >>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> >0.001 sec
> >>> -
> >>> in org.apache.syncope.fit.console.AjaxPalettePanelITCase
> >>> Running org.apache.syncope.fit.console.AjaxTextFieldITCase
> >>> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> >0.003 sec
> >>> -
> >>> in org.apache.syncope.fit.console.AjaxTextFieldITCase
> >>> Running org.apache.syncope.fit.console.AnyObjectsITCase
> >>> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> >18.317 sec
> >>> - in org.apache.syncope.fit.console.AnyObjectsITCase
> >>> Running org.apache.syncope.fit.console.AnyTypeClassesITCase
> >>> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> >15.733 sec
> >>> - in org.apache.syncope.fit.console.AnyTypeClassesITCase
> >>> Running org.apache.syncope.fit.console.AnyTypesITCase
> >>> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> >8.887 sec
> >>> -
> >>> in org.apache.syncope.fit.console.AnyTypesITCase
> >>> Running org.apache.syncope.fit.console.BulkActionITCase
> >>> Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> >44.265 sec
> >>> - in org.apache.syncope.fit.console.BulkActionITCase
> >>> Running org.apache.syncope.fit.console.DisplayAttributesITCase
> >>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> >0.905 sec
> >>> -
> >>> in org.apache.syncope.fit.console.DisplayAttributesITCase
> >>> Running org.apache.syncope.fit.console.GroupsITCase
> >>> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> >23.918 sec
> >>> - in org.apache.syncope.fit.console.GroupsITCase
> >>> Running org.apache.syncope.fit.console.LogsITCase
> >>> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> >3.603 sec
> >>> -
> >>> in org.apache.syncope.fit.console.LogsITCase
> >>> Running org.apache.syncope.fit.console.NotificationsITCase
> >>> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> >15.384 sec
> >>> - in org.apache.syncope.fit.console.NotificationsITCase
> >>> Running org.apache.syncope.fit.console.ParametersITCase
> >>> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> >6.092 sec
> >>> -
> >>> in org.apache.syncope.fit.console.ParametersITCase
> >>> Running org.apache.syncope.fit.console.PoliciesITCase
> >>> Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> >51.494
> >>> sec
> >>> - in org.apache.syncope.fit.console.PoliciesITCase
> >>> Running org.apache.syncope.fit.console.RealmsITCase
> >>> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> >12.745 sec
> >>> - in

Re: [GSOC 2017] [SYNCOPE-152] Support SCIM REST API

2017-03-13 Thread Supun Wanniarachchi 
Hi,

I have go through the descriptions on JIRA issue and have a good
understanding on SCIM 1.1 and 2.0. I have already setup the Syncope project
environment and successfully build the project. And also I have tried some
open source products [1] they're already using SCIM  2.0 APIs. I would like
to know what are the steps and requirements I have to follow, before come
up with the project proposal. Your prompt attention to this matter is
greatly appreciated.

[1] https://github.com/wso2-extensions/identity-inbound-provisioning-scim2

Thank you,

On Thu, Mar 2, 2017 at 2:16 PM, Supun Wanniarachchi 
wrote:

> Hi Francesco,
>
> Thanks a lot for your quick response. I'll look into these and get back to
> you.
>
> Cheers,
>
> On Thu, Mar 2, 2017 at 1:54 PM, Francesco Chicchiriccò <
> ilgro...@apache.org> wrote:
>
>> Hi,
>> I have added some description to the issue on JIRA to clarify the scope
>> and purpose of this activity.
>> Please take a look.
>>
>> Regards.
>>
>> On 02/03/2017 05:58, Supun Wanniarachchi wrote:
>>
>>> Hi All,
>>>
>>> I am Supun Wanniarachchi, a 3rd year undergraduate at Informatics
>>> Institute
>>> of Technology, Sri Lanka (Affiliated with University of Westminster, UK)
>>> studying Software Engineering. I have successfully completed GSoC last
>>> year
>>> also with Moodle [1].
>>> I'm familiar with Microservices, SOA, and API. I just looked the SCIM
>>> documentation
>>> [2] and seems pretty much interesting. So I would like to contribute this
>>> project and it would be great if you could provide more details of the
>>> project and guide me through the process.
>>>
>>> [1] https://summerofcode.withgoogle.com/archive/2016/projects/58
>>> 76476796731392
>>> [2] http://www.simplecloud.info/specs/draft-scim-api-00.html
>>>
>>
>> --
>> Francesco Chicchiriccò
>>
>> Tirasa - Open Source Excellence
>> http://www.tirasa.net/
>>
>> Member at The Apache Software Foundation
>> Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
>> http://home.apache.org/~ilgrosso/
>>
>>
>
>
> --
> Supun Wanniarachchi
> Software Engineering Undergraduate
> Informatics Institute of Technology Sri Lanka (Affiliated with University
> of Westminster, UK)
> Mobile: +94 716326119 <+94%2071%20632%206119>
> Blog: http://blog.supun.me
> [image: https://lk.linkedin.com/in/supun-wanniarachchi-21b37a97]
> 
>



-- 
Supun Wanniarachchi
Software Engineering Undergraduate
Informatics Institute of Technology Sri Lanka (Affiliated with University
of Westminster, UK)
Mobile: +94 716326119
Blog: http://blog.supun.me
[image: https://lk.linkedin.com/in/supun-wanniarachchi-21b37a97]