[
https://issues.apache.org/jira/browse/SYNCOPE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720643#comment-13720643
]
Andrei Shakirin commented on SYNCOPE-285:
-
Hi Francesco,
I think these met
[
https://issues.apache.org/jira/browse/SYNCOPE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720596#comment-13720596
]
Andrei Shakirin commented on SYNCOPE-285:
-
+1 from me.
Can not believe tha
[
https://issues.apache.org/jira/browse/SYNCOPE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720593#comment-13720593
]
Andrei Shakirin commented on SYNCOPE-285:
-
@GET
@Path("{t
[
https://issues.apache.org/jira/browse/SYNCOPE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720587#comment-13720587
]
Andrei Shakirin commented on SYNCOPE-285:
-
Hi Francesco,
As far as I reme
[
https://issues.apache.org/jira/browse/SYNCOPE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720491#comment-13720491
]
Andrei Shakirin commented on SYNCOPE-246:
-
Aah, now I got it.
Let us resolv
[
https://issues.apache.org/jira/browse/SYNCOPE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720485#comment-13720485
]
Andrei Shakirin commented on SYNCOPE-246:
-
Hi Francesco,
Yeah, if that br
[
https://issues.apache.org/jira/browse/SYNCOPE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718321#comment-13718321
]
Andrei Shakirin commented on SYNCOPE-246:
-
> hence I wonder whether
[
https://issues.apache.org/jira/browse/SYNCOPE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718310#comment-13718310
]
Andrei Shakirin commented on SYNCOPE-246:
-
Hi Francesco,
I try to explain
+1 from me as well. I think I can also support Jan with removing Spring MVC in
two-three weeks.
Regards,
Andrei.
> -Original Message-
> From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
> Sent: Montag, 29. April 2013 15:20
> To: dev@syncope.apache.org
> Subject: Work start on 1.2
+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:
>
>
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
+1 (non binding)
Cheers,
Andrei.
> -Original Message-
> From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
> Sent: Freitag, 5. April 2013 13:29
> To: dev@syncope.apache.org
> Subject: [VOTE] Apache Syncope 1.1.0
>
> I've created a 1.1.0 release, with the following artifacts up for
+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 Ir
> 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
Hi Francesco,
Do you see any ways to resolve the problem through:
a) increase default 2 minutes timeout
b) optimize cargo Syncope startup (not sure is it really possible)
?
Cheers,
Andrei.
> -Original Message-
> From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
> Sent: Freitag,
[
https://issues.apache.org/jira/browse/SYNCOPE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin resolved SYNCOPE-335.
-
Resolution: Fixed
> Use correct wrapper names for returning li
Andrei Shakirin created SYNCOPE-335:
---
Summary: Use correct wrapper names for returning lists
Key: SYNCOPE-335
URL: https://issues.apache.org/jira/browse/SYNCOPE-335
Project: Syncope
Issue
[
https://issues.apache.org/jira/browse/SYNCOPE-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin reassigned SYNCOPE-335:
---
Assignee: Andrei Shakirin
> Use correct wrapper names for returning li
> Sent: Sonntag, 10. März 2013 16:35
> To: dev@syncope.apache.org
> Subject: Re: ?!?
>
> 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.
>
che.org]
> Sent: Freitag, 8. März 2013 09:10
> To: dev@syncope.apache.org
> Subject: Re: ?!?
>
> On 07/03/2013 23:41, Andrei Shakirin wrote:
> > Hi Francesco,
> >
> > As Sergei already explained, JAXB produces this name from annotation
> @XmlRootElement(name = "
Hi Francesco,
As Sergei already explained, JAXB produces this name from annotation
@XmlRootElement(name = "policy") in PolicyTO class.
In case of List it adds "s" suffix to root element name.
I will care about the solution.
Regards,
Andrei.
> -Original Message-
> From: Francesco Chicch
+1 for "Apache Syncope authentication" for now.
Potentially can be customized as well.
> -Original Message-
> From: Sergey Beryozkin [mailto:sberyoz...@gmail.com]
> Sent: Donnerstag, 28. Februar 2013 17:40
> To: dev@syncope.apache.org
> Subject: Re: BasicAuth realm String
>
> On 27/02/13
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:
iriccò [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.
>
Hi,
We have finally all JAX-RS integration tests green.
To minimize the risk of breaking JAX-RS interface by further 1.1.0
changes/fixes, I would propose any of two ways:
1. Just ask all committers to run -Pjaxrs profile before any 1.1.0 commit
2. Activate JAX-RS tests additionally
[
https://issues.apache.org/jira/browse/SYNCOPE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574468#comment-13574468
]
Andrei Shakirin commented on SYNCOPE-136:
-
Thanks for fix an
[
https://issues.apache.org/jira/browse/SYNCOPE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574463#comment-13574463
]
Andrei Shakirin commented on SYNCOPE-136:
-
Oops, sorry, Francesco ... it
[
https://issues.apache.org/jira/browse/SYNCOPE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13574406#comment-13574406
]
Andrei Shakirin commented on SYNCOPE-136:
-
Hi Francesco,
Could you please
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"));
use
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573803#comment-13573803
]
Andrei Shakirin commented on SYNCOPE-231:
-
I am in vacation until 19.08.
[
https://issues.apache.org/jira/browse/SYNCOPE-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin closed SYNCOPE-298.
---
Resolution: Won't Fix
Wouldn't be fixed because of another solution with pre-conf
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) Fi
apache.org
> Subject: Re: [DISCUSSION] Integration tests instability causes by Ids
> collision
> (AUTO generation strategy)
>
> On 02/02/2013 10:10, Andrei Shakirin wrote:
> > Hi,
> >
> > Analyses shows, that real reason of failed/unstable tests is not AUTO
> ge
[
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 migrat
Hi,
Analyses shows, that real reason of failed/unstable tests is not AUTO
generation strategy itself as reported in [1], but collision between newly
created and pre-configured entries.
Actually following entities have AUTO generation strategy:
- AbstractDerAttr
- AbstractVirAttr
- Notification
-
that is the
> > case, we have to decide---really---whether checked //exceptions are
> > worth their price./ / /
>
> Here some more similar articles:
> http://tapestryjava.blogspot.in/2011/05/tragedy-of-checked-
> exceptions.html
> http://blogs.atlassian.com/2011/05/exce
gt; -Original Message-
> From: 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
Hi Francesco,
I thought it was agreed in [1]. Have seen no objections in [2].
Do you have reasons to keep this exception checked?
Regards,
Andrei.
[1] https://cwiki.apache.org/confluence/display/SYNCOPE/Remote+Exceptions
[2]
http://syncope-dev.1063484.n5.nabble.com/Exception-propagation-in-Res
after today's work, I am able to successfully
> build
> with JDK 1.7 - I guess you've found the way to cope with existing ids in the
> test content.xml and the ids generated during test execution, nice!
>
> Regards.
>
> On 30/01/2013 13:43, Andrei Shakirin wrote:
&g
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
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] htt
Hi,
Found ... explore SVN client required to add new files explicitly.
All tests including console were successful, but two most important file was
not committed, super :(
Will use command line client only in the future.
Regards,
Andrei.
> -Original Message-
> From: Francesco Chicchiri
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-
> tools/src/main/resources/org
ò [mailto:ilgro...@apache.org]
> 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 Wo
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
> Su
[
https://issues.apache.org/jira/browse/SYNCOPE-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566604#comment-13566604
]
Andrei Shakirin commented on SYNCOPE-298:
-
Possible reason of the problem c
Hi Francesco,
I have problem under jdk 1.7 as well, but in other test!
Running org.apache.syncope.core.rest.UserTestITCase
Tests run: 52, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 33.524 sec <<<
FAILURE!
testEnforceMandatoryConditionOnDerived(org.apache.syncope.core.rest.UserTestITCa
se)
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565426#comment-13565426
]
Andrei Shakirin commented on SYNCOPE-231:
-
I am merging it now.
Unfortuna
[
https://issues.apache.org/jira/browse/SYNCOPE-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565353#comment-13565353
]
Andrei Shakirin commented on SYNCOPE-298:
-
Hi Francesco,
Again, this Issu
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-tabpanel&focusedCommentId=13565247#comment-13565247
]
Andrei Shakirin commented on SYNCOPE-231:
-
Hi Francesco,
> Andrei, I gu
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565221#comment-13565221
]
Andrei Shakirin commented on SYNCOPE-231:
-
>Andrei,
>any news about
t UsertTestITCase.issueSYNCOPE279
>
>
> Il giorno 29/gen/2013, alle ore 10.10, Andrei Shakirin ha scritto:
>
> > Hi Fabio,
> >
> >> Hi Andrei, I found the problem: into the
> >> AbstractPropagationTaskExecutor, line 334, the call to
> >> getR
: Re: [Question] Problem with test 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(
Hi,
I am analysing problem regarding UsertTestITCase.issueSYNCOPE279().
It is reproducible in following situations:
1) Run it as single test: mvn -Pdev -DwaitForCheck=false -Dit.test=
UserTestITCase# issueSYNCOPE279
Because of some reasons this test is succeed in case if
AuthenticationTes
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564170#comment-13564170
]
Andrei Shakirin commented on SYNCOPE-231:
-
Hi Francesco,
I have used only
[
https://issues.apache.org/jira/browse/SYNCOPE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564155#comment-13564155
]
Andrei Shakirin commented on SYNCOPE-289:
-
Hi Francesco,
Yep, it is expecte
[
https://issues.apache.org/jira/browse/SYNCOPE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563592#comment-13563592
]
Andrei Shakirin commented on SYNCOPE-289:
-
Introduced -Pjaxrs profile activa
,
Andrei.
> -Original Message-
> From: Andrei Shakirin [mailto:ashaki...@talend.com]
> Sent: Samstag, 26. Januar 2013 17:59
> To: dev@syncope.apache.org
> Subject: RE: [Discuss] Way to parameterize integration tests
>
> Hi Francesco,
>
> > > 2. Leave
ry to commit until Monday.
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/20
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:
http://junit.sourceforge.net/javadoc/o
[
https://issues.apache.org/jira/browse/SYNCOPE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562611#comment-13562611
]
Andrei Shakirin commented on SYNCOPE-289:
-
I am afraid it cased by @Run
[
https://issues.apache.org/jira/browse/SYNCOPE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561641#comment-13561641
]
Andrei Shakirin commented on SYNCOPE-289:
-
Should be fixed now, sorry
[
https://issues.apache.org/jira/browse/SYNCOPE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561611#comment-13561611
]
Andrei Shakirin commented on SYNCOPE-289:
-
Sorry, will care abou
11:29
> To: dev@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
Issue Type: Sub-task
> > Components: console, core
> >Reporter: Andrei Shakirin
> >Assignee: Andrei Shakirin
> > Fix For: 1.2.0
> >
> >
>
>
> --
> This message is automatically generated by JIRA.
> If
[
https://issues.apache.org/jira/browse/SYNCOPE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin updated SYNCOPE-289:
Issue Type: Sub-task (was: Bug)
Parent: SYNCOPE-231
> Prepare CXF R
[
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
[
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 to
[
https://issues.apache.org/jira/browse/SYNCOPE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560758#comment-13560758
]
Andrei Shakirin commented on SYNCOPE-289:
-
Hi Francesco,
It is not
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-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin resolved SYNCOPE-256.
-
Resolution: Fixed
> Update Rest exception mapper to Apache
I think it is good to
> have developers build and test on different platforms.
> >
> > Best regards.
> > Jan
> >
> >>>>> -Original Message-
> >>>>> From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
> >>>>>
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 f
inal Message-
> From: 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
Hi,
> I generally agree with the concept of returning created with the location in
> create methods. The problem is though that our service interface has no
> method to get the object based on the location.
Pragmatic solution is returning URI as well as business object ID in Response
object.
In
[
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 s
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,
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 exi
ct: Re: [DISCUSS] Moving issues from one version to another
>
> On 21/01/2013 15:04, Andrei Shakirin wrote:
> >> Hum, I actually thought you would have included the full CXF features
> >> in
> >> 1.1.0 alongside with still running but deprecated Spring MVC interfaces
> Hum, I actually thought you would have included the full CXF features in
> 1.1.0 alongside with still running but deprecated Spring MVC interfaces.
> If I was wrong, could this be done?
It will be optimal for us, as far as we resolver list setters issue for TOs
mentioned by Jan.
What about int
Hi Francesco,
+1 from my side for all four topics.
Cheers,
Andrei.
> -Original Message-
> From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
> Sent: Montag, 21. Januar 2013 11:46
> To: dev@syncope.apache.org
> Subject: [DISCUSS] Moving issues from one version to another
>
> Hi al
13 11:25
> To: dev@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
gt; Sent: Montag, 21. Januar 2013 11:00
> To: dev@syncope.apache.org
> Subject: Re: [Discussion] Rest package names
>
> On 21.01.2013 10:29, Andrei Shakirin wrote:
> > Hi,
> >
> > I would like to make a proposal regarding some Rest package names:
> >
> >
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.
Andrei Shakirin created SYNCOPE-282:
---
Summary: Implement JAX-RS exception mapper for server side
Key: SYNCOPE-282
URL: https://issues.apache.org/jira/browse/SYNCOPE-282
Project: Syncope
[
https://issues.apache.org/jira/browse/SYNCOPE-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin updated SYNCOPE-280:
Fix Version/s: 1.1.0
> Update some checked exceptions to runtime o
[
https://issues.apache.org/jira/browse/SYNCOPE-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Shakirin resolved SYNCOPE-280.
-
Resolution: Fixed
> Update some checked exceptions to runtime o
[
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 bu
[
https://issues.apache.org/jira/browse/SYNCOPE-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13557319#comment-13557319
]
Andrei Shakirin commented on SYNCOPE-280:
-
InvalidPolicyType will be
Andrei Shakirin created SYNCOPE-280:
---
Summary: Update some checked exceptions to runtime ones
Key: SYNCOPE-280
URL: https://issues.apache.org/jira/browse/SYNCOPE-280
Project: Syncope
Issue
HTTP header vs body
> for details
>
> On 18/01/2013 15:04, Andrei Shakirin wrote:
> > Hi,
> >
> > From proposals regarding remote exceptions in [1], I am going to do the
> following during CXF migration:
> > 1) Update HTTP mapping codes (see "Mapping
t;)
WDYT?
Cheers,
Andrei.
> -Original Message-
> From: Andrei Shakirin [mailto:ashaki...@talend.com]
> Sent: Montag, 7. Januar 2013 10:01
> To: dev@syncope.apache.org
> Subject: RE: Exception propagation in Rest interface: HTTP header vs body for
> details
>
> I ha
[
https://issues.apache.org/jira/browse/SYNCOPE-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13557213#comment-13557213
]
Andrei Shakirin commented on SYNCOPE-268:
-
Actually all tests are re-runn
> 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
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
Entitle
Hi Francesco,
> Sorry Jan, I don't think this fact is inline with community-driven
> development.
>
> This community discussed and established a roadmap with some releases
> [2]: this roadmap can be reviewed over time, of course, but it remains the
> driver for this project's activities, indeed.
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 (Revisio
iginal Message-
> From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
> Sent: 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
1 - 100 of 162 matches
Mail list logo
