Re: [REQUEST] Checking admin console on trunk
Hi, Il giorno 29/dic/2013, alle ore 15:30, Fabio Martelli fabio.marte...@gmail.com ha scritto: Il 27/12/2013 15:33, Francesco Chicchiriccò ha scritto: Hi all, in the last days I've been cleaning up the admin console code on trunk with a couple of targets: (a) using SpinnerFieldPanel (a field panel using JQuery UI's spinner [1]) everywhere possible and (b) remove Xlint:unchecked compiler warnings. I did some careful tests (besides Selenium's of course), but since I had to make a lot of (often non-trivial) changes, it would be cool if someone can take some time to intensively check all admin console features. I find two error: 1) I edit a policy and change type to Global Policy, the core returns an internal server error. 2) After executing a report, select the type of report to download, Apache Syncope returns a Wicket Error. Regards Marco Regards. [1] http://jqueryui.com/spinner/ I'm not sure if you can be interested by https://issues.apache.org/jira/browse/SYNCOPE-465 Regards, F. -- Fabio Martelli Tirasa - Open Source Excellence http://www.tirasa.net/ Apache Syncope PMC http://people.apache.org/~fmartelli/ -- Dott. Marco Di Sabatino Di Diodoro Tel. +39 3939065570 Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973 http://www.tirasa.net Apache Syncope PMC Member http://people.apache.org/~mdisabatino/
[jira] [Created] (SYNCOPE-466) Server error when updating an existing policy to its global counterpart
Francesco Chicchiriccò created SYNCOPE-466: -- Summary: Server error when updating an existing policy to its global counterpart Key: SYNCOPE-466 URL: https://issues.apache.org/jira/browse/SYNCOPE-466 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.5 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.6, 1.2.0 As reported in mailing list [1], when either a global policy and 'normal' policy exist (for password, for example), updating the latter as being 'global' triggers an Internal Server Error instead of a checked error. [1] http://markmail.org/message/drs6mrwfuiig3af2 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Re: [REQUEST] Checking admin console on trunk
On 30/12/2013 10:28, Marco Di Sabatino Di Diodoro wrote: Hi, Il giorno 29/dic/2013, alle ore 15:30, Fabio Martelli fabio.marte...@gmail.com ha scritto: Il 27/12/2013 15:33, Francesco Chicchiriccò ha scritto: Hi all, in the last days I've been cleaning up the admin console code on trunk with a couple of targets: (a) using SpinnerFieldPanel (a field panel using JQuery UI's spinner [1]) everywhere possible and (b) remove Xlint:unchecked compiler warnings. I did some careful tests (besides Selenium's of course), but since I had to make a lot of (often non-trivial) changes, it would be cool if someone can take some time to intensively check all admin console features. I find two errors: 1) I edit a policy and change type to Global Policy, the core returns an internal server error. This also affects 1_1_X, hence it is again unrelated to my latest changes; anyway I've opened SYNCOPE-466. 2) After executing a report, select the type of report to download, Apache Syncope returns a Wicket Error. Just fixed in http://svn.apache.org/r1554177 Regards. [1] http://jqueryui.com/spinner/ I'm not sure if you can be interested by https://issues.apache.org/jira/browse/SYNCOPE-465 Regards, F. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
[Fixed] apache/syncope#401 (trunk - 5cd906b)
Build Update for apache/syncope - Build: #401 Status: Fixed Duration: 9 minutes and 39 seconds Commit: 5cd906b (trunk) Author: Francesco Chicchiriccò Message: Handling missing HTTP location git-svn-id: https://svn.apache.org/repos/asf/syncope/trunk@1554177 13f79535-47bb-0310-9956-ffa450edef68 View the changeset: https://github.com/apache/syncope/compare/989c4557cc39...5cd906b4fe8e View the full build log and details: https://travis-ci.org/apache/syncope/builds/16134292 -- You can configure recipients for build notifications in your .travis.yml file. See http://about.travis-ci.org/docs/user/build-configuration
[jira] [Commented] (SYNCOPE-466) Server error when updating an existing policy to its global counterpart
[ https://issues.apache.org/jira/browse/SYNCOPE-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13858718#comment-13858718 ] ASF subversion and git services commented on SYNCOPE-466: - Commit 1554190 from [~ilgrosso] in branch 'syncope/trunk' [ https://svn.apache.org/r1554190 ] [SYNCOPE-466] Merge from 1_1_X Server error when updating an existing policy to its global counterpart --- Key: SYNCOPE-466 URL: https://issues.apache.org/jira/browse/SYNCOPE-466 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.5 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.6, 1.2.0 As reported in mailing list [1], when either a global policy and 'normal' policy exist (for password, for example), updating the latter as being 'global' triggers an Internal Server Error instead of a checked error. [1] http://markmail.org/message/drs6mrwfuiig3af2 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[Tirasa/SyncopeCamel] fd318a: fixed issue #12
Branch: refs/heads/trunk Home: https://github.com/Tirasa/SyncopeCamel Commit: fd318a29f5492c618ab65f0f7626217ef28ee9e6 https://github.com/Tirasa/SyncopeCamel/commit/fd318a29f5492c618ab65f0f7626217ef28ee9e6 Author: Giacomo Lamonaco giacomo.lamon...@tirasa.net Date: 2013-12-30 (Mon, 30 Dec 2013) Changed paths: R core/src/main/java/org/apache/syncope/core/camel/CamelProvisioningManager.java A core/src/main/java/org/apache/syncope/core/camel/CamelUserProvisioningManager.java M core/src/main/java/org/apache/syncope/core/camel/RoleProvisioningManager.java A core/src/main/java/org/apache/syncope/core/camel/processors/DefaultUserDeprovisionPropagation.java M core/src/main/resources/camelRoute.xml M core/src/main/resources/syncopeContext.xml Log Message: --- fixed issue #12
[jira] [Assigned] (SYNCOPE-465) Selected items lost browsing paged results
[ https://issues.apache.org/jira/browse/SYNCOPE-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-465: -- Assignee: Francesco Chicchiriccò Selected items lost browsing paged results -- Key: SYNCOPE-465 URL: https://issues.apache.org/jira/browse/SYNCOPE-465 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.6, 1.2.0 Reporter: fabio martelli Assignee: Francesco Chicchiriccò Fix For: 1.1.6, 1.2.0 Selected items lost browsing paged results. The issue can be observed browsing resources from 'Resources' tab: 1. select items (like to be done to perform bulk actions) 2. move yourself among resource list, page per page 3. come back at the selection page ... you will found your previous selection forgotten. Of course, the problem doesn't regard resources specifically. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
Persistence Layer in Syncope, Table Creation, orm.xml, content.xml
Hi there I'm looking into adding a persistence layer to the Apache Fediz Identity Provider and used the persistence layer in Syncope as a good reference. Nevertheless, I got a few questions... 1) JPA creates the tables when the first entity is added - usually triggered by a REST call. They won't be created when the spring application context is loaded. The Syncope ContentLoader does only add rows to existing tables and creates indexes and views, but no tables. How did you workaround this? 2) What was the reason for you to create an orm.xml instead of using annotations only? 3) You introduced your own semantic of a file to import default data (content.xml). I assume you did not use an SQL script to be independent of the database? But why did you use the JDBC template instead of the JPA layer? Thanks a lot for your Feedback. Oli
[jira] [Commented] (SYNCOPE-465) Selected items lost browsing paged results
[ https://issues.apache.org/jira/browse/SYNCOPE-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13859396#comment-13859396 ] ASF subversion and git services commented on SYNCOPE-465: - Commit 1554382 from [~ilgrosso] in branch 'syncope/trunk' [ https://svn.apache.org/r1554382 ] [SYNCOPE-465] Merge from 1_1_X Selected items lost browsing paged results -- Key: SYNCOPE-465 URL: https://issues.apache.org/jira/browse/SYNCOPE-465 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.6, 1.2.0 Reporter: fabio martelli Assignee: Francesco Chicchiriccò Fix For: 1.1.6, 1.2.0 Selected items lost browsing paged results. The issue can be observed browsing resources from 'Resources' tab: 1. select items (like to be done to perform bulk actions) 2. move yourself among resource list, page per page 3. come back at the selection page ... you will found your previous selection forgotten. Of course, the problem doesn't regard resources specifically. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (SYNCOPE-465) Selected items lost browsing paged results
[
https://issues.apache.org/jira/browse/SYNCOPE-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13859401#comment-13859401
]
Francesco Chicchiriccò commented on SYNCOPE-465:
The commits above don't actually solve this issue: adding
{{AjaxFormChoiceComponentUpdatingBehavior}} to {{CheckGroup}} in
{{AjaxDataTablePanel}} makes this scenario working (in Resources tab):
# select an item from page 1
# move to page 2
# move back to page 1
# page 1 shows selected item from step 1 above
while this scenario is still now working:
# select an item from page 1
# move to page 2
# select an item from page 2
# move back to page 1
# page 1 shows no selected items
Besides this, {{ActionDataTablePanel}} - e.g. on users status modal window, for
example - does not work even from simpler case.
Selected items lost browsing paged results
--
Key: SYNCOPE-465
URL: https://issues.apache.org/jira/browse/SYNCOPE-465
Project: Syncope
Issue Type: Bug
Components: console
Affects Versions: 1.1.6, 1.2.0
Reporter: fabio martelli
Assignee: Francesco Chicchiriccò
Fix For: 1.1.6, 1.2.0
Selected items lost browsing paged results.
The issue can be observed browsing resources from 'Resources' tab:
1. select items (like to be done to perform bulk actions)
2. move yourself among resource list, page per page
3. come back at the selection page
... you will found your previous selection forgotten.
Of course, the problem doesn't regard resources specifically.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
