syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SYNCOPE-1062) Changes pulled from one resource not propagated externally
Date Thu, 06 Apr 2017 12:32:41 GMT

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

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

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

[SYNCOPE-1062] Better management of @Transactional with Propagation.REQUIRES_NEW for create
/ update / delete during pull


> Changes pulled from one resource not propagated externally
> ----------------------------------------------------------
>
>                 Key: SYNCOPE-1062
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1062
>             Project: Syncope
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.0.2
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>             Fix For: 2.0.3, 2.1.0
>
>
> Let's suppose to have:
> # resource R1 supporting user propagation
> # group G with resource R1 assigned
> # resource R2 supporting user pull
> # pull task T for R2, with user template set for granting G membership
> When executing T the first time, user U is created internally and propagated to R1, as
expected.
> If U is modified on R2 (attribute change), when T is executed again the expected change
is reflected on U internally. Nothing is changed, however, on R1.
> If U is modified on R2 again and T executed the third time, the expected change is still
reflected on U internally. R1, however, receives the change coming from the former T execution.



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

Mime
View raw message