[
https://issues.apache.org/jira/browse/SYNCOPE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13720587#comment-13720587
]
Andrei Shakirin commented on SYNCOPE-285:
-
Hi Francesco,
As far as I remember
[
https://issues.apache.org/jira/browse/SYNCOPE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13720596#comment-13720596
]
Andrei Shakirin commented on SYNCOPE-285:
-
+1 from me.
Can not believe that we
[
https://issues.apache.org/jira/browse/SYNCOPE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13720643#comment-13720643
]
Andrei Shakirin commented on SYNCOPE-285:
-
Hi Francesco,
I think these methods
[
https://issues.apache.org/jira/browse/SYNCOPE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13718310#comment-13718310
]
Andrei Shakirin commented on SYNCOPE-246:
-
Hi Francesco,
I try to explain
+1 (non-binding)
-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Donnerstag, 18. April 2013 11:06
To: dev@syncope.apache.org
Subject: [VOTE] Apache Syncope 1.0.8
I've created a 1.0.8 release, with the following artifacts up for a vote:
SVN
Hi Francesco,
Hi all,
we had some discussion in the past about random errors with Java 7 and the
-Pjaxrs Maven profile.
Today I have updated CXF from 2.7.3 to 2.7.4 and most of such errors seems
to disappear (I've been executing some times -Pjaxrs with either OpenJDK 7
and Oracle JDK 7 on
+1 for extending SyncopeAuthenticationProvider.
-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Freitag, 29. März 2013 08:48
To: dev@syncope.apache.org
Subject: Re: [DISCUSS] Migrating users from 1.0.X to 1.1.0
On 28/03/2013 18:58, Guido
Hi Francesco,
I don't see why the merges for SYNCOPE-203 need to be reverted as they are
not breaking anything. I would prefer to leave things as they are but not
claim full OSGi support in the 1.1.0 release.
I guess you are concerned that these issues will hold up the 1.1.0 release and
, 8. März 2013 09:10
To: dev@syncope.apache.org
Subject: Re: policys/ ?!?
On 07/03/2013 23:41, Andrei Shakirin wrote:
Hi Francesco,
As Sergei already explained, JAXB produces this name from annotation
@XmlRootElement(name = policy) in PolicyTO class.
In case of ListT extends PolicyTO
:35
To: dev@syncope.apache.org
Subject: Re: policys/ ?!?
On 10/03/2013 16:10, Andrei Shakirin wrote:
Thanks: it is also for me the chance to get a bit insight this new
CXF layer that will be soon the only layer available.
OK, then just ping us if you have any problems with a fix.
I
Hi Francesco,
As Sergei already explained, JAXB produces this name from annotation
@XmlRootElement(name = policy) in PolicyTO class.
In case of ListT extends PolicyTO it adds s suffix to root element name.
I will care about the solution.
Regards,
Andrei.
-Original Message-
From:
Hi Francesco,
+1 for issue.
Find it also quite dangerous, create() should throw exception if entity already
exists, 409 Conflict will be corresponded HTTP error code in this case.
Regards,
Andrei.
-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent:
[mailto:ilgro...@apache.org]
Sent: Freitag, 8. Februar 2013 18:13
To: dev@syncope.apache.org
Subject: Re: [DISCUSS] JAXRS integration tests
On 08/02/2013 16:54, Andrei Shakirin wrote:
Hi,
We have finally all JAX-RS integration tests green.
To minimize the risk of breaking JAX-RS interface
Hi Francesco,
Could you please care about re-run ability also in new integration tests?
UserTestITCase.readWithMailAddressAsUserName() should look like:
@Test
public void readWithMailAddressAsUserName() {
UserTO userTO = createUser(getUniqueSampleTO(m...@domain.org));
[
https://issues.apache.org/jira/browse/SYNCOPE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13574406#comment-13574406
]
Andrei Shakirin commented on SYNCOPE-136:
-
Hi Francesco,
Could you please care
[
https://issues.apache.org/jira/browse/SYNCOPE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin resolved SYNCOPE-289.
-
Resolution: Fixed
Prepare CXF Rest integration tests migration
Hi,
Would like to shortly report status of CXF migration:
It is basically finished. We still have 2 Failures and 4 Errors in JAXRS tests
- it should be fixed in next days (the reason of two is already clear).
Still open for 1.1.0 (SYNCOPE -231):
1) Fix rest errors in tests (6)
2)
: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Freitag, 1. Februar 2013 14:37
To: dev@syncope.apache.org
Subject: Re: IncompatiblePolicyException was made unchecked
On 01/02/2013 14:33, Andrei Shakirin wrote:
Hi Francesco,
I thought it was agreed in [1]. Have seen
://misko.hevery.com/2009/09/16/checked-exceptions-i-love-you-but-
you-have-to-go/
Christian
Am 01.02.2013 14:36, schrieb Francesco Chicchiriccò:
On 01/02/2013 14:33, Andrei Shakirin wrote:
Hi Francesco,
I thought it was agreed in [1]. Have seen no objections in [2].
You're right about [1] and [2
Hi,
Related topic: I going to use AttributableType in WorkflowService instead
strings user and role.
Any objections?
Regards,
Andrei.
-Original Message-
From: Jan Bernhardt [mailto:jbernha...@talend.com]
Sent: Donnerstag, 31. Januar 2013 09:58
To: dev@syncope.apache.org
Subject:
]
Sent: Donnerstag, 31. Januar 2013 11:48
To: dev@syncope.apache.org
Subject: Re: [DISCUSS] SchemaType and SchemaService
On 31/01/2013 11:30, Andrei Shakirin wrote:
Hi,
Related topic: I going to use AttributableType in WorkflowService instead
strings user and role.
Any objections
Hi Francesco,
I care about it ...
Andrei.
-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Donnerstag, 31. Januar 2013 12:50
To: dev@syncope.apache.org
Subject: Re: svn commit: r1440904 - in /syncope/trunk: build-
Hi,
We have implemented two proposals from [1] by CXF migration.
I am going to create Jira issues for rest two:
1) Mapping to SyncopeClientCompositeException on client side
2) Mapping low level exceptions in core
and schedule them to 1.3.0?
Any objections?
Regards,
Andrei.
[1]
Andrei Shakirin created SYNCOPE-303:
---
Summary: Mapping to SyncopeClientCompositeException on client side
Key: SYNCOPE-303
URL: https://issues.apache.org/jira/browse/SYNCOPE-303
Project: Syncope
Andrei Shakirin created SYNCOPE-304:
---
Summary: Mapping low level exceptions in core
Key: SYNCOPE-304
URL: https://issues.apache.org/jira/browse/SYNCOPE-304
Project: Syncope
Issue Type
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565221#comment-13565221
]
Andrei Shakirin commented on SYNCOPE-231:
-
Andrei,
any news about the errors
Andrei Shakirin created SYNCOPE-298:
---
Summary: Persistence beans: change AUTO Id generation strategy to
TABLE
Key: SYNCOPE-298
URL: https://issues.apache.org/jira/browse/SYNCOPE-298
Project
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565426#comment-13565426
]
Andrei Shakirin commented on SYNCOPE-231:
-
I am merging it now.
Unfortunately
[
https://issues.apache.org/jira/browse/SYNCOPE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13564155#comment-13564155
]
Andrei Shakirin commented on SYNCOPE-289:
-
Hi Francesco,
Yep, it is expected
UsertTestITCase.issueSYNCOPE279
Hi Andrei, answers and comment inline.
Il giorno 28/gen/2013, alle ore 16.09, Andrei Shakirin ha scritto:
Hi,
I am analysing problem regarding UsertTestITCase.issueSYNCOPE279().
It is reproducible in following situations:
1) Run it as single
.
Andrei.
-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Freitag, 25. Januar 2013 18:01
To: dev@syncope.apache.org
Subject: Re: [Discuss] Way to parameterize integration tests
On 25/01/2013 17:39, Andrei Shakirin wrote:
Hi,
One more topic
[
https://issues.apache.org/jira/browse/SYNCOPE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562611#comment-13562611
]
Andrei Shakirin commented on SYNCOPE-289:
-
I am afraid it cased by @RunWith
Hi,
One more topic to discuss:
Currently integration tests run using communication using JSON contentType only.
For new CXF-based tests we are going to run every tests twice: with XML and
JSON [1].
JUnit proposes elegant solution using parameterized tests:
@syncope.apache.org
Subject: Re: [Discussion] Prepare CXF Rest integration tests migration
On 24/01/2013 10:57, Andrei Shakirin wrote:
Hi,
Do you have any objections, if I prepare and commit duplicates of rest
integration tests for JAX-RS (CXF) in separate package, but wouldn't activate
them in 1.1.0
[
https://issues.apache.org/jira/browse/SYNCOPE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13561641#comment-13561641
]
Andrei Shakirin commented on SYNCOPE-289:
-
Should be fixed now, sorry
[
https://issues.apache.org/jira/browse/SYNCOPE-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin resolved SYNCOPE-282.
-
Resolution: Fixed
Implement JAX-RS exception mapper for server side
: Jan Bernhardt [mailto:jbernha...@talend.com]
Sent: Mittwoch, 23. Januar 2013 10:41
To: dev@syncope.apache.org
Subject: RE: [DISCUSS] New REST Service Interfaces - ConfigurationService
-Original Message-
From: Andrei Shakirin [mailto:ashaki...@talend.com]
Sent: Mittwoch, 23
Hi,
I am currently cannot build archetype (Apache Syncope sample project) from
trunk with an error:
[INFO] [ERROR] Unknown lifecycle phase #. You must specify a valid lifecycle
...
I see the similar problem in Jenkins build for 1_0_X branch, but not for the
trunk.
Has anybody clue how to fix
[
https://issues.apache.org/jira/browse/SYNCOPE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin resolved SYNCOPE-256.
-
Resolution: Fixed
Update Rest exception mapper to Apache CXF
Andrei Shakirin created SYNCOPE-289:
---
Summary: Prepare CXF Rest integration tests migration
Key: SYNCOPE-289
URL: https://issues.apache.org/jira/browse/SYNCOPE-289
Project: Syncope
Issue
[
https://issues.apache.org/jira/browse/SYNCOPE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13560758#comment-13560758
]
Andrei Shakirin commented on SYNCOPE-289:
-
Hi Francesco,
It is not very important
[
https://issues.apache.org/jira/browse/SYNCOPE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin updated SYNCOPE-289:
Fix Version/s: (was: 1.2.0)
1.1.0
Description: Moving back
[
https://issues.apache.org/jira/browse/SYNCOPE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin updated SYNCOPE-289:
Issue Type: Bug (was: Sub-task)
Parent: (was: SYNCOPE-231)
Prepare CXF
Hi,
Regarding the ResourceDataTest, I have sporadically one of three problems:
1) java.lang.OutOfMemoryError: PermGen space
2) Test and JVM hang
3) The forked VM terminated without saying properly goodbye. VM crash or
System.exit called.
For me it looks like memory problem with unpredictable
Thanks Francesco,
Problem is resolved!
Andrei.
-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Dienstag, 22. Januar 2013 11:06
To: dev@syncope.apache.org
Subject: Re: [Question] ApplicationContextProvider in UnitTests
On 22/01/2013 10:11,
Hi,
I would like to make a proposal regarding some Rest package names:
1. Core services implementations: org.apache.syncope.core.services
(actually org.apache.syncope.core.services.impl). Impl ending doesn't bring
additional information and doesn't recommended by java best practices.
names
On 21.01.2013 10:29, Andrei Shakirin wrote:
Hi,
I would like to make a proposal regarding some Rest package names:
1. Core services implementations: org.apache.syncope.core.services
(actually org.apache.syncope.core.services.impl). Impl ending doesn't
bring additional
@syncope.apache.org
Subject: Re: [Discussion] Rest package names
On 21.01.2013 11:14, Andrei Shakirin wrote:
Hi Christian,
2. Resource comparators and server exception mapper:
org.apache.syncope.core.rest.utils (actually
org.apache.syncope.core.rest).
It makes purpose of these classes more
Names will be Consistent. New CXF REST Services will all End with *Service.
Old Spring Services currently ending with *Controller will eventually all
vanish, once new Services are actually used (migration is complete).
Than is absolutely OK for me. + 1.
Andrei.
Best regards.
Jan
[
https://issues.apache.org/jira/browse/SYNCOPE-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13557213#comment-13557213
]
Andrei Shakirin commented on SYNCOPE-268:
-
Actually all tests are re-runnable
a duplicate key
is found: this is not happening (under normal conditions) for a server fault
but for a client's.
2) Update some checked exceptions to runtime ones (see Checked vs
Runtime exceptions)
Sounds reasonable.
Regards.
-Original Message-
From: Andrei Shakirin
[
https://issues.apache.org/jira/browse/SYNCOPE-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13557319#comment-13557319
]
Andrei Shakirin commented on SYNCOPE-280:
-
InvalidPolicyType will be also
[
https://issues.apache.org/jira/browse/SYNCOPE-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin resolved SYNCOPE-268.
-
Resolution: Fixed
Enable Rest IntegrationTests to run more than once (per build
Hi,
Any ideas why this build yesterday was failed?
Do not get it, all tests seems to be ok ...
Seems that failure was caused by my change:
Integrated in Syncope-trunk #439 (See
[https://builds.apache.org/job/Syncope-trunk/439/])
[SYNCOPE-268] Make rest integration tests re-runnable
Hi Jan,
=== Renaming Service ===
Rename AuthenticationController to EntitlementService(Impl), since
containing methods have little to nothing to do with authentication. It is
only
about Entitlements...
+1 for Entitlement, -1 for Service. I would keep names consistently, if use
Hi,
I have two questions regarding tasks in context of SYNCOPE-268:
1) Is there easy way to create Notification and Propagation tasks?
Tests issueSyncope81() and deal() delete preconfigured Propagation task (id=1)
and Notification task (id=8).
To make tests re-runnable I need to
: Mittwoch, 16. Januar 2013 13:12
To: dev@syncope.apache.org
Subject: Re: [Question] Tasks related questions
On 16/01/2013 13:03, Fabio Martelli wrote:
Il giorno 16/gen/2013, alle ore 11.57, Andrei Shakirin ha scritto:
Hi,
I have two questions regarding tasks in context of SYNCOPE-268
supported DBs. Corresponded JIRA issue will be created for it.
Does it sounds reasonable?
Cheers,
Andrei.
-Original Message-
From: Andrei Shakirin [mailto:ashaki...@talend.com]
Sent: Freitag, 11. Januar 2013 12:01
To: dev@syncope.apache.org
Subject: RE: Persistence id generation strategy
Hi,
Fabio and Francesco: thanks for the fast feedback.
I cannot remember the good reason for this differences but it there was ...
In our experience with Apache Syncope (especially at the beginning) there
are troubles with AUTO generated id in case of high concurrence.
Not only: some
[
https://issues.apache.org/jira/browse/SYNCOPE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13551076#comment-13551076
]
Andrei Shakirin commented on SYNCOPE-259:
-
For PolicyService, SchemaService
[
https://issues.apache.org/jira/browse/SYNCOPE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543754#comment-13543754
]
Andrei Shakirin commented on SYNCOPE-259:
-
Hi Jan,
Thanks, looks perfect now.
(3
[
https://issues.apache.org/jira/browse/SYNCOPE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin updated SYNCOPE-259:
Comment: was deleted
(was: yep, connectorStatus sounds better (it not always physical
[
https://issues.apache.org/jira/browse/SYNCOPE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543790#comment-13543790
]
Andrei Shakirin commented on SYNCOPE-259:
-
Hi Jan,
Why do you think @GET
[
https://issues.apache.org/jira/browse/SYNCOPE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13542833#comment-13542833
]
Andrei Shakirin commented on SYNCOPE-259:
-
I will start with ResourceController
[
https://issues.apache.org/jira/browse/SYNCOPE-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin updated SYNCOPE-259:
Attachment: ResourceService.patch
Added patch for ResourceService.
Essential changes
[
https://issues.apache.org/jira/browse/SYNCOPE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin updated SYNCOPE-251:
Attachment: cxf-deps.patch
Fix Dependency issues with ConnID Bundle deployment
[
https://issues.apache.org/jira/browse/SYNCOPE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13535808#comment-13535808
]
Andrei Shakirin commented on SYNCOPE-251:
-
Hi Francesco,
Jan is in vacation
[
https://issues.apache.org/jira/browse/SYNCOPE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin updated SYNCOPE-256:
Attachment: Unauthorized.patch
Updates for exception mappers + integration test
[
https://issues.apache.org/jira/browse/SYNCOPE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin updated SYNCOPE-256:
Attachment: ExceptionMapperUserTests.patch
Updated UserTestItCase for CXF ExceptionMapper
[
https://issues.apache.org/jira/browse/SYNCOPE-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin updated SYNCOPE-256:
Attachment: syncopeClientError.jsp.patch
Hi Jan,
Two test cases are failed because
. Dezember 2012 18:34
To: dev@syncope.apache.org
Subject: Re: Exception propagation in Rest interface: HTTP header vs body
for details
On 13/12/12 16:45, Francesco Chicchiriccò wrote:
On 13/12/2012 14:27, Sergey Beryozkin wrote:
Hi
On 13/12/12 12:42, Andrei Shakirin wrote:
Hi,
I am
Andrei Shakirin created SYNCOPE-256:
---
Summary: Update Rest exception mapper to Apache CXF
Key: SYNCOPE-256
URL: https://issues.apache.org/jira/browse/SYNCOPE-256
Project: Syncope
Issue
into
separate project
On 10/12/2012 10:40, Andrei Shakirin wrote:
Hi Francesco,
Yep, we need kind of plan to synchronize our work.
I see the following order:
1. Merge the DEV_ROLE_PROVISIONING (Francesco) 2. Separate
persistence
layer SYNCOPE-241, SYNCOPE-242 (Christian) 3
Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Mittwoch, 12. Dezember 2012 10:48
To: dev@syncope.apache.org
Subject: Re: [DISCUSS] Re: Extract syncope system/integration tests into
separate project
On 12/12/2012 10:44, Andrei Shakirin wrote:
Hi Francesco,
I still see some benefits to extract
Hi Francesco,
I would propose to close discussion with -1 for now without creating jira issue.
If community will see this refactoring necessary in the future we can reopen
the discussion.
For sure we have actually more urgent and important things to process.
Do you agree?
Cheers,
Andrei.
Andrei Shakirin created SYNCOPE-247:
---
Summary: Use complete UUID as role name to avoid problems by test
rerun
Key: SYNCOPE-247
URL: https://issues.apache.org/jira/browse/SYNCOPE-247
Project
76 matches
Mail list logo
