On 31/01/2013 19:01, Colm O hEigeartaigh wrote:
Hi Francesco,
So, this must be the issue: with Chrome, Enter submits the whole form, with Firefox
instead the "Add" button in the derived attributes tab is triggered. Odd...
Cool, that's the error alright (on Firefox). Hitting 'enter' in either
[
https://issues.apache.org/jira/browse/SYNCOPE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567995#comment-13567995
]
Hudson commented on SYNCOPE-295:
Integrated in Syncope-trunk #50 (See
[https://builds.ap
Hi Francesco,
> So, this must be the issue: with Chrome, Enter submits the whole form,
with Firefox instead the "Add" button in the derived attributes > tab is
triggered. Odd...
Cool, that's the error alright (on Firefox). Hitting 'enter' in either a
attribute or virtual attribute textbox causes
[
https://issues.apache.org/jira/browse/SYNCOPE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved SYNCOPE-295.
-
Resolution: Fixed
> If AccountId is selected when creating a Resource Mappin
[
https://issues.apache.org/jira/browse/SYNCOPE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Massimiliano Perrone resolved SYNCOPE-210.
--
Resolution: Fixed
http://svn.apache.org/viewvc?rev=1441074&view=rev
[
https://issues.apache.org/jira/browse/SYNCOPE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567853#comment-13567853
]
Hudson commented on SYNCOPE-210:
Integrated in Syncope-trunk #49 (See
[https://builds.ap
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567854#comment-13567854
]
Hudson commented on SYNCOPE-231:
Integrated in Syncope-trunk #49 (See
[https://builds.ap
On 30/01/2013 08:43, Francesco Chicchiriccò wrote:
On 30/01/2013 08:41, Jan Bernhardt wrote:
Hi Francesco,
Yes, I will take care of this. It was on my agenda to update
documentation site by today.
Great, thank you Jan.
Jan,
"TODO: Is this a good design decision? Should these activities be
Hi Andrei,
I just want to report that, 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:
H
On 31/01/2013 17:44, Colm O hEigeartaigh wrote:
Hi Francesco,
However, I am not sure to understand exactly how to replicate this: are you
creating an user and hitting enter when populating attribute values? If so, I
guess this happens with roles as well, isn’t it?
Yep exactly. Fill in userna
Hi Francesco,
> However, I am not sure to understand exactly how to replicate this: are
you creating an user and hitting enter when populating attribute
> values? If so, I guess this happens with roles as well, isn’t it?
Yep exactly. Fill in username + password, enter some random string for an
at
On 31/01/2013 17:28, Colm O hEigeartaigh wrote:
Hi guys,
I'm seeing a console error on trunk somewhat similar to SYNCOPE-297. The
scenario here is the propagation of a user with a simple User attribute to
a backend. If I enter the attribute without hitting 'enter' it propagates
fine. If I create
[
https://issues.apache.org/jira/browse/SYNCOPE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567780#comment-13567780
]
Hudson commented on SYNCOPE-297:
Integrated in Syncope-trunk #48 (See
[https://builds.ap
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567781#comment-13567781
]
Hudson commented on SYNCOPE-231:
Integrated in Syncope-trunk #48 (See
[https://builds.ap
Hi guys,
I'm seeing a console error on trunk somewhat similar to SYNCOPE-297. The
scenario here is the propagation of a user with a simple User attribute to
a backend. If I enter the attribute without hitting 'enter' it propagates
fine. If I create another user, enter the value for the attribute +
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: Impr
[
https://issues.apache.org/jira/browse/SYNCOPE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh resolved SYNCOPE-297.
-
Resolution: Fixed
> External Attributes are showing up for AccoundId/Passwor
[
https://issues.apache.org/jira/browse/SYNCOPE-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567724#comment-13567724
]
Hudson commented on SYNCOPE-298:
Integrated in Syncope-trunk #47 (See
[https://builds.ap
> -Original Message-
> From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
> Sent: Donnerstag, 31. Januar 2013 15:58
> To: dev@syncope.apache.org
> Subject: Re: [DISCUSS] Two Jira issues for Exceptions
>
> On 31/01/2013 15:54, Andrei Shakirin wrote:
> > Hi,
> >
> > We have implemente
On 31/01/2013 15:54, Andrei Shakirin wrote:
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
Fine.
and schedule the
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
[
https://issues.apache.org/jira/browse/SYNCOPE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567678#comment-13567678
]
Colm O hEigeartaigh commented on SYNCOPE-297:
-
Hi Francesco,
Great thanks -
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567670#comment-13567670
]
Hudson commented on SYNCOPE-231:
Integrated in Syncope-trunk #46 (See
[https://builds.ap
[
https://issues.apache.org/jira/browse/SYNCOPE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò updated SYNCOPE-297:
---
Attachment: syncope-297-ilgrosso.patch
I've made some further investigation
[
https://issues.apache.org/jira/browse/SYNCOPE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567653#comment-13567653
]
Francesco Chicchiriccò commented on SYNCOPE-297:
Hi Colm,
your patch look
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567590#comment-13567590
]
Hudson commented on SYNCOPE-231:
Integrated in Syncope-trunk #44 (See
[https://builds.ap
[
https://issues.apache.org/jira/browse/SYNCOPE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-128.
Resolution: Fixed
Hi Denis,
I've made some rework around your original pag
The Apache Jenkins build system has built Syncope-trunk (build #43)
Status: Fixed
Check console output at https://builds.apache.org/job/Syncope-trunk/43/ to view
the results.
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567581#comment-13567581
]
Hudson commented on SYNCOPE-231:
Integrated in Syncope-trunk #43 (See
[https://builds.ap
[
https://issues.apache.org/jira/browse/SYNCOPE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567580#comment-13567580
]
Hudson commented on SYNCOPE-302:
Integrated in Syncope-trunk #43 (See
[https://builds.ap
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
[
https://issues.apache.org/jira/browse/SYNCOPE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colm O hEigeartaigh updated SYNCOPE-297:
Attachment: syncope-297.patch
Hi guys,
I'd like some feedback on the attached pat
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
Hi Andrei,
as stated by latest failures on Jenkins, it seems that your commit broke
the build, in particular your modification to
core/src/main/resources/restContent.xml adds a reference to
workflowServiceImpl that cannot be resolved by Spring.
Have you forgotten to commit something else or j
The Apache Jenkins build system has built Syncope-trunk (build #42)
Status: Aborted
Check console output at https://builds.apache.org/job/Syncope-trunk/42/ to view
the results.
The Apache Jenkins build system has built Syncope-trunk (build #41)
Status: Aborted
Check console output at https://builds.apache.org/job/Syncope-trunk/41/ to view
the results.
The Apache Jenkins build system has built Syncope-trunk (build #40)
Status: Failure
Check console output at https://builds.apache.org/job/Syncope-trunk/40/ to view
the results.
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567564#comment-13567564
]
Hudson commented on SYNCOPE-231:
Integrated in Syncope-trunk #40 (See
[https://builds.ap
[
https://issues.apache.org/jira/browse/SYNCOPE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567563#comment-13567563
]
Hudson commented on SYNCOPE-302:
Integrated in Syncope-trunk #40 (See
[https://builds.ap
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567532#comment-13567532
]
Hudson commented on SYNCOPE-231:
Integrated in Syncope-trunk #39 (See
[https://builds.ap
> None if you take care in the code that AttirbutableType can also be
> MEMBERSHIP in general while in the workflow context this is naturally
> meaningless.
Sure, it will BadRequest in case of MEMBERSHIP.
Andrei.
> -Original Message-
> From: Francesco Chicchiriccò [mailto:ilgro...@apache
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?
None if you take care in the code that AttirbutableType can also be
MEMBERSHIP in general while in the workflow context this is
On 31/01/2013 09:58, Jan Bernhardt wrote:
Hi Syncoper,
We know three different schema types in syncope "normal Schema", "derived Schema" and
"virtual Schema". In Spring REST Interface these schemas are mapped to three different controllers
which are basically doing the same thing, just for eac
[
https://issues.apache.org/jira/browse/SYNCOPE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-302.
Resolution: Fixed
http://svn.apache.org/viewvc?rev=1440901&view=rev
Francesco Chicchiriccò created SYNCOPE-302:
--
Summary: Error when accessing the Resources page as non-admin
Key: SYNCOPE-302
URL: https://issues.apache.org/jira/browse/SYNCOPE-302
Project: Sync
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
+1, it sounds good to me.
Regards
JB
On 01/31/2013 09:58 AM, Jan Bernhardt wrote:
Hi Syncoper,
We know three different schema types in syncope "normal Schema", "derived Schema" and
"virtual Schema". In Spring REST Interface these schemas are mapped to three different controllers
which are ba
Il giorno 31/gen/2013, alle ore 09.58, Jan Bernhardt ha scritto:
> Hi Syncoper,
>
> We know three different schema types in syncope "normal Schema", "derived
> Schema" and "virtual Schema". In Spring REST Interface these schemas are
> mapped to three different controllers which are basically d
Hi Syncoper,
We know three different schema types in syncope "normal Schema", "derived
Schema" and "virtual Schema". In Spring REST Interface these schemas are mapped
to three different controllers which are basically doing the same thing, just
for each type.
Therefore I only created a single
[
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567466#comment-13567466
]
Hudson commented on SYNCOPE-231:
Integrated in Syncope-trunk #38 (See
[https://builds.ap
51 matches
Mail list logo
