[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562948#comment-13562948
]
Hudson commented on SYNCOPE-231:
Integrated in Syncope-trunk #12 (See
[https://builds.ap
On 25.01.2013 17:30, Francesco Chicchiriccò wrote:
> On 25/01/2013 17:28, Christian Schneider wrote:
>> On 25.01.2013 17:18, Francesco Chicchiriccò wrote:
>>> I also thought about this and if I should rather wait. My change only
affects the new interface. So the old controller stays the same a
On 25/01/2013 17:39, Andrei Shakirin wrote:
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
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562831#comment-13562831
]
Hudson commented on SYNCOPE-231:
Integrated in Syncope-trunk #11 (See
[https://builds.ap
[
https://issues.apache.org/jira/browse/SYNCOPE-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562820#comment-13562820
]
Francesco Chicchiriccò commented on SYNCOPE-122:
Idea for this feature in
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
On 25/01/2013 17:28, Christian Schneider wrote:
On 25.01.2013 17:18, Francesco Chicchiriccò wrote:
I also thought about this and if I should rather wait. My change only
affects the new interface. So the old controller stays the same and
stays active. The change should not affect anyone who uses
On 25.01.2013 17:18, Francesco Chicchiriccò wrote:
> I also thought about this and if I should rather wait. My change only
>> affects the new interface. So the old controller stays the same and
>> stays active. The change should not affect anyone who uses the current
>> spring based rest interface.
On 25/01/13 16:18, Christian Schneider wrote:
On 25.01.2013 17:11, Sergey Beryozkin wrote:
Hi Christian
On 25/01/13 15:56, Christian Schneider wrote:
When doing the CXF version of the UserRequestService I found that our
current UserRequestController does not really follow the rest ideas.
The
On 25.01.2013 17:11, Sergey Beryozkin wrote:
> Hi Christian
>
> On 25/01/13 15:56, Christian Schneider wrote:
>> When doing the CXF version of the UserRequestService I found that our
>> current UserRequestController does not really follow the rest ideas.
>>
>> The problem is that it does follow the
On 25/01/2013 17:13, Christian Schneider wrote:
On 25.01.2013 17:07, Francesco Chicchiriccò wrote:
On 25/01/2013 16:56, Christian Schneider wrote:
When doing the CXF version of the UserRequestService I found that our
current UserRequestController does not really follow the rest ideas.
The prob
On 25.01.2013 17:07, Francesco Chicchiriccò wrote:
> On 25/01/2013 16:56, Christian Schneider wrote:
>> When doing the CXF version of the UserRequestService I found that our
>> current UserRequestController does not really follow the rest ideas.
>>
>> The problem is that it does follow the idea of
Hi Christian
On 25/01/13 15:56, Christian Schneider wrote:
When doing the CXF version of the UserRequestService I found that our
current UserRequestController does not really follow the rest ideas.
The problem is that it does follow the idea of doing CRUD operations on
resources. Some methods w
On 25/01/2013 16:56, Christian Schneider wrote:
When doing the CXF version of the UserRequestService I found that our
current UserRequestController does not really follow the rest ideas.
The problem is that it does follow the idea of doing CRUD operations on
resources. Some methods work with use
Hi all,
I was working on the admin console, saw the commit of revision 1438558,
updated and... completely locked out.
When starting the admin console via mvn -Pdev I have in the logs a long
stacktrace ending with:
Caused by: java.lang.NullPointerException: null
at
org.apache.syncope.cli
[
https://issues.apache.org/jira/browse/SYNCOPE-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562800#comment-13562800
]
Hudson commented on SYNCOPE-122:
Integrated in Syncope-trunk #10 (See
[https://builds.ap
When doing the CXF version of the UserRequestService I found that our
current UserRequestController does not really follow the rest ideas.
The problem is that it does follow the idea of doing CRUD operations on
resources. Some methods work with userId others with requestId. So for
example the are
Hi Christian,
could you please explain the rationale of the modifications below - e.g.
why previous
userRequestService.create()
userRequestService.update()
userRequestService.delete()
all become
userRequestService.create()
?
I find this quite confusing...
Regards.
On 25/01/2013 16:43, cs
Francesco Chicchiriccò created SYNCOPE-290:
--
Summary: Typed SyncopeConf
Key: SYNCOPE-290
URL: https://issues.apache.org/jira/browse/SYNCOPE-290
Project: Syncope
Issue Type: Improveme
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562732#comment-13562732
]
Hudson commented on SYNCOPE-231:
Integrated in Syncope-trunk #9 (See
[https://builds.apa
[
https://issues.apache.org/jira/browse/SYNCOPE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562733#comment-13562733
]
Hudson commented on SYNCOPE-275:
Integrated in Syncope-trunk #9 (See
[https://builds.apa
[
https://issues.apache.org/jira/browse/SYNCOPE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-136:
---
Description:
Currently, cleartext password is always required when subscribi
[
https://issues.apache.org/jira/browse/SYNCOPE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-136:
---
Description:
Currently, cleartext password is always required when subscribi
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562694#comment-13562694
]
Jan Bernhardt commented on SYNCOPE-231:
---
Hi Francesco,
I had similar results with
[
https://issues.apache.org/jira/browse/SYNCOPE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-275.
Resolution: Fixed
http://svn.apache.org/viewvc?rev=1438506&view=rev
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562669#comment-13562669
]
Francesco Chicchiriccò commented on SYNCOPE-231:
After latest modificatio
[
https://issues.apache.org/jira/browse/SYNCOPE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-135:
---
Fix Version/s: (was: 1.1.0)
3.0.0
> Password rese
[
https://issues.apache.org/jira/browse/SYNCOPE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-135:
---
Issue Type: Sub-task (was: New Feature)
Parent: SYNCOPE-160
> P
[
https://issues.apache.org/jira/browse/SYNCOPE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562664#comment-13562664
]
Marco Di Sabatino Di Diodoro commented on SYNCOPE-135:
--
+1
M
--
+1
M
On Jan 25, 2013, at 1:23 PM, Francesco Chicchiriccò (JIRA) wrote:
>
>[
> https://issues.apache.org/jira/browse/SYNCOPE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562625#comment-13562625
> ]
>
> Francesco Chicchiriccò commented on S
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562659#comment-13562659
]
Hudson commented on SYNCOPE-231:
Integrated in Syncope-trunk #8 (See
[https://builds.apa
[
https://issues.apache.org/jira/browse/SYNCOPE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562645#comment-13562645
]
fabio martelli commented on SYNCOPE-135:
+1
> Password reset
> -
[
https://issues.apache.org/jira/browse/SYNCOPE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562636#comment-13562636
]
Francesco Chicchiriccò commented on SYNCOPE-289:
Ok, I will then change i
[
https://issues.apache.org/jira/browse/SYNCOPE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562625#comment-13562625
]
Francesco Chicchiriccò commented on SYNCOPE-135:
Agree to move this issue
[
https://issues.apache.org/jira/browse/SYNCOPE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562618#comment-13562618
]
Massimiliano Perrone commented on SYNCOPE-135:
--
Hi guys,
this morning I have
[
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 @RunWith(Param
[
https://issues.apache.org/jira/browse/SYNCOPE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562608#comment-13562608
]
Francesco Chicchiriccò commented on SYNCOPE-289:
Prior to latest modifica
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13562588#comment-13562588
]
Hudson commented on SYNCOPE-231:
Integrated in Syncope-trunk #7 (See
[https://builds.apa
[
https://issues.apache.org/jira/browse/SYNCOPE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-275:
---
Issue Type: Improvement (was: Sub-task)
Parent: (was: SYNCOPE-28
[
https://issues.apache.org/jira/browse/SYNCOPE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò reassigned SYNCOPE-275:
--
Assignee: Francesco Chicchiriccò
> Upgrade Spring to 3.2.1
> -
[
https://issues.apache.org/jira/browse/SYNCOPE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-275:
---
Description:
Spring 3.2.0 has been out for a while now; this new release int
[
https://issues.apache.org/jira/browse/SYNCOPE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-275:
---
Fix Version/s: (was: 1.2.0)
1.1.0
> Upgrade Sprin
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Bernhardt updated SYNCOPE-231:
--
Attachment: TaskService.patch
I do not understand why this patch (TaskService) breaks
UserTes
43 matches
Mail list logo
