[jira] [Commented] (SYNCOPE-289) Prepare CXF Rest integration tests migration
[ https://issues.apache.org/jira/browse/SYNCOPE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566308#comment-13566308 ] Hudson commented on SYNCOPE-289: Integrated in Syncope-trunk #30 (See [https://builds.apache.org/job/Syncope-trunk/30/]) [SYNCOPE-289] * Adding missing TestCases * Code cleanup (Revision 1440300) Result = SUCCESS jbernhardt : Files : * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/ConfigurationTestITCaseJAXRS.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/ConnectorTestITCaseJAXRS.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/EntitlementTestITCaseJAXRS.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/LoggerTestITCaseJAXRS.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/NotificationTestITCaseJAXRS.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/PolicyTestITCaseJAXRS.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/ReportTestITCaseJAXRS.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/ResourceTestITCaseJAXRS.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/RoleTestITCaseJAXRS.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/SchemaTestITCaseJAXRS.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/TaskTestITCaseJAXRS.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/UserRequestTestITCaseJAXRS.java > Prepare CXF Rest integration tests migration > > > Key: SYNCOPE-289 > URL: https://issues.apache.org/jira/browse/SYNCOPE-289 > Project: Syncope > Issue Type: Sub-task > Components: console, core >Reporter: Andrei Shakirin >Assignee: Andrei Shakirin > Fix For: 1.1.0 > > > Moving back to 1.1.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[DISCUSS] Feed Item Query Language
Hi Syncopers, I'm currently working on updating our CXF migration website [1]. While I was starting documentation some month ago, I discovered a nice feature CXF offers, to make more standard like search queries, that can easily be applied to different persistent layers. It is called "Feed Item Query Language"(FIQL). Take a look at [2] for more detailed information. We are currently using our own custom *Cond classes to POST search requests. According to RESTful best practices it would be nicer, to send these kind of search queries via GET operation. With FIQL we could easily achieve this behavior. So my proposal would be to create a new JIRA ticket (for 1.3.0 ?) to switch our current implementation to support and use FIQL search queries in the feature, and also update our Roadmap accordingly. WDYT? Best regards. Jan [1] https://cwiki.apache.org/confluence/display/SYNCOPE/REST+API+upgrade#RESTAPIupgrade-ConfigurationService [2] http://cxf.apache.org/docs/jax-rs-search.html
[jira] [Commented] (SYNCOPE-231) Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack)
[ https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566356#comment-13566356 ] Hudson commented on SYNCOPE-231: Integrated in Syncope-trunk #31 (See [https://builds.apache.org/job/Syncope-trunk/31/]) [SYNCOPE-231] Fixed JAXRS ConnectorTestITCaseJAXRS (Revision 1440324) [SYNCOPE-231][SYNCOPE-289] * Fixing UserService * Removing RestTemplate dependencies from IT tests * Code cleanup (Revision 1440323) Result = SUCCESS ashakirin : Files : * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/ConnInstanceTestITCase.java jbernhardt : Files : * /syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/RoleServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/UserRequestServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/UserServiceProxy.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/UserRequestRestClient.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/LoggerServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/NotificationServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/PolicyServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/ReportServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/ResourceServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/RoleServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/SchemaServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/UserRequestServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/UserServiceImpl.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AbstractTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AuthenticationTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/RoleTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserRequestTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java > Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack) > -- > > Key: SYNCOPE-231 > URL: https://issues.apache.org/jira/browse/SYNCOPE-231 > Project: Syncope > Issue Type: Improvement > Components: console, core >Reporter: Jan Bernhardt >Assignee: Jan Bernhardt > Fix For: 1.1.0 > > Attachments: TaskService.patch > > > Current REST Interfaces are based on Spring Webservice framework. > Goal of this task is to replace Spring with CXF and to relay on JAX-B and > JAX-RS annotations rather then Spring annotations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-289) Prepare CXF Rest integration tests migration
[ https://issues.apache.org/jira/browse/SYNCOPE-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566357#comment-13566357 ] Hudson commented on SYNCOPE-289: Integrated in Syncope-trunk #31 (See [https://builds.apache.org/job/Syncope-trunk/31/]) [SYNCOPE-231][SYNCOPE-289] * Fixing UserService * Removing RestTemplate dependencies from IT tests * Code cleanup (Revision 1440323) Result = SUCCESS jbernhardt : Files : * /syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/RoleServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/UserRequestServiceProxy.java * /syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/UserServiceProxy.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/UserRequestRestClient.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/LoggerServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/NotificationServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/PolicyServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/ReportServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/ResourceServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/RoleServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/SchemaServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/UserRequestServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/UserServiceImpl.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AbstractTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AuthenticationTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/RoleTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserRequestTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java > Prepare CXF Rest integration tests migration > > > Key: SYNCOPE-289 > URL: https://issues.apache.org/jira/browse/SYNCOPE-289 > Project: Syncope > Issue Type: Sub-task > Components: console, core >Reporter: Andrei Shakirin >Assignee: Andrei Shakirin > Fix For: 1.1.0 > > > Moving back to 1.1.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Build not working (again) with JDK 1.7
Hi all,
unfortunately, after latest updates since yesterday afternoon when I did
my last checks, the build on JDK 1.7 is failing again:
Results :
Failed tests:
UserTestITCase.create:481 expected:<166> but was:<165>
UserTestITCase.verifyTaskRegistration:1000 expected:<187> but was:<186>
Tests in error:
TaskTestITCase.sync:325 » SyncopeClientCompositeError {[NotFound
[User test0]]...
With JDK 1.6 no problems (as Jenkins confirms).
Both behaviours seems to be stable.
Andrei told me yesterday that this is not the case, but just for sake of
completeness, let's think again if this is related to SYNCOPE-298.
If not, what can be the reason of these failures with JDK 1.7?
Regards.
--
Francesco Chicchiriccò
ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
Re: [DISCUSS] Feed Item Query Language
On 30/01/2013 11:27, Jan Bernhardt wrote: Hi Syncopers, I'm currently working on updating our CXF migration website [1]. While I was starting documentation some month ago, I discovered a nice feature CXF offers, to make more standard like search queries, that can easily be applied to different persistent layers. It is called "Feed Item Query Language"(FIQL). Take a look at [2] for more detailed information. We are currently using our own custom *Cond classes to POST search requests. According to RESTful best practices it would be nicer, to send these kind of search queries via GET operation. With FIQL we could easily achieve this behavior. So my proposal would be to create a new JIRA ticket (for 1.3.0 ?) to switch our current implementation to support and use FIQL search queries in the feature, and also update our Roadmap accordingly. WDYT? +1 - if there is a standard (AFAIU is [3]) I don't see any reason to stuck with our custom way. A mandatory statement for this change is, of course, to not reduce the space of possible conditions that can be currently searched for. I also agree with targeting this change to 1.3.0. Regards. [1] https://cwiki.apache.org/confluence/display/SYNCOPE/REST+API+upgrade#RESTAPIupgrade-ConfigurationService [2] http://cxf.apache.org/docs/jax-rs-search.html [3] http://tools.ietf.org/html/draft-nottingham-atompub-fiql-00 -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
Re: Discuss: Move InvalidSearchConditionException to common
I changed the exception to unchecked only till we have a decision to make the service interface work. I will move the exception to common and make it checked again like discussed. Christian Am 30.01.2013 08:29, schrieb Francesco Chicchiriccò: On 28/01/2013 15:38, Francesco Chicchiriccò wrote: On 28/01/2013 15:36, Christian Schneider wrote: Currently InvalidSearchConditionException is in core.persistence.dao and is a checked exception. If we want to make this exception part of the UserService interface to have it available on the client we will have to move it to common. Currently the console does not seem to use the exception on the client side. So my preliminary solution to get it running is to make the exception unchecked so I can pass it to the exception mapper without having it in the interface. So basically the two things to discuss are if we want to move the exception to common and if we want to make it unchecked. I personally would do both. This exception is not used by the admin console because the code is done so that no invalid search conditions are sent to the core; however, other clients are likely to need this exception to be returned. Hence: +1 for moving it to common, but don't see enough reason to make it unchecked. I've noticed that this issue was moved to common as unchecked: any additional reason behind not leaving it checked than the need to change some interface method's signature? Regards. -- Christian Schneider http://www.liquid-reality.de Open Source Architect Talend Application Integration Division http://www.talend.com
Re: [DISCUSS] Feed Item Query Language
Hi On 30/01/13 10:43, Francesco Chicchiriccò wrote: On 30/01/2013 11:27, Jan Bernhardt wrote: Hi Syncopers, I'm currently working on updating our CXF migration website [1]. While I was starting documentation some month ago, I discovered a nice feature CXF offers, to make more standard like search queries, that can easily be applied to different persistent layers. It is called "Feed Item Query Language"(FIQL). Take a look at [2] for more detailed information. We are currently using our own custom *Cond classes to POST search requests. According to RESTful best practices it would be nicer, to send these kind of search queries via GET operation. With FIQL we could easily achieve this behavior. So my proposal would be to create a new JIRA ticket (for 1.3.0 ?) to switch our current implementation to support and use FIQL search queries in the feature, and also update our Roadmap accordingly. WDYT? +1 - if there is a standard (AFAIU is [3]) I don't see any reason to stuck with our custom way. A mandatory statement for this change is, of course, to not reduce the space of possible conditions that can be currently searched for. IMHO using FIQL can definitely be interesting: it can expand the space indeed, in a way which is not always easy to do with simple queries, so +1 to getting FIQL supported; That said, in addition, I'd also consider offering a simple/typical name/value query interface to let users who are most comfortable with using plain name/value pairs to use them as usual - but also offer a more enhanced FIQL-powered interface - I guess this flexibility can be supported without too much extra complexity, with a single Search service only... Thanks, Sergey I also agree with targeting this change to 1.3.0. Regards. [1] https://cwiki.apache.org/confluence/display/SYNCOPE/REST+API+upgrade#RESTAPIupgrade-ConfigurationService [2] http://cxf.apache.org/docs/jax-rs-search.html [3] http://tools.ietf.org/html/draft-nottingham-atompub-fiql-00
[jira] [Assigned] (SYNCOPE-299) Add "row to display" selector in resources
[ https://issues.apache.org/jira/browse/SYNCOPE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned SYNCOPE-299: --- Assignee: Colm O hEigeartaigh > Add "row to display" selector in resources > -- > > Key: SYNCOPE-299 > URL: https://issues.apache.org/jira/browse/SYNCOPE-299 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 1.0.5 >Reporter: Denis Signoretto >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.6, 1.1.0 > > > Allow resources list to display more than 10 resources per page (add the > "Rows to display" pager) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (SYNCOPE-300) Supporting Feed Item Query Language (FIQL)
Jan Bernhardt created SYNCOPE-300: - Summary: Supporting Feed Item Query Language (FIQL) Key: SYNCOPE-300 URL: https://issues.apache.org/jira/browse/SYNCOPE-300 Project: Syncope Issue Type: Improvement Components: common, console, core Reporter: Jan Bernhardt Priority: Minor Fix For: 1.3.0 Currently search conditions are build using custom components (org.apache.syncope.common.search.*), goal of this issue is to replace current implementation with support for "Supporting Feed Item Query Language" (FIQL). For more details take a look at the discussion in development mailing list: http://syncope-dev.1063484.n5.nabble.com/DISCUSS-Feed-Item-Query-Language-td5712490.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
RE: [DISCUSS] Feed Item Query Language
Jira issue created: https://issues.apache.org/jira/browse/SYNCOPE-300 What a magic number ;-) Best regards. Jan > -Original Message- > From: Sergey Beryozkin [mailto:sberyoz...@gmail.com] > Sent: Mittwoch, 30. Januar 2013 11:50 > To: dev@syncope.apache.org > Subject: Re: [DISCUSS] Feed Item Query Language > > Hi > On 30/01/13 10:43, Francesco Chicchiriccò wrote: > > On 30/01/2013 11:27, Jan Bernhardt wrote: > >> Hi Syncopers, > >> > >> I'm currently working on updating our CXF migration website [1]. > >> While I was starting documentation some month ago, I discovered a > >> nice feature CXF offers, to make more standard like search queries, > >> that can easily be applied to different persistent layers. It is > >> called "Feed Item Query Language"(FIQL). Take a look at [2] for more > >> detailed information. > >> > >> We are currently using our own custom *Cond classes to POST search > >> requests. According to RESTful best practices it would be nicer, to > >> send these kind of search queries via GET operation. With FIQL we > >> could easily achieve this behavior. > >> > >> So my proposal would be to create a new JIRA ticket (for 1.3.0 ?) to > >> switch our current implementation to support and use FIQL search > >> queries in the feature, and also update our Roadmap accordingly. > >> > >> WDYT? > > > > +1 - if there is a standard (AFAIU is [3]) I don't see any reason to > > stuck with our custom way. > > A mandatory statement for this change is, of course, to not reduce the > > space of possible conditions that can be currently searched for. > > > > IMHO using FIQL can definitely be interesting: it can expand the space > indeed, in a way which is not always easy to do with simple queries, so > +1 to getting FIQL supported; > That said, in addition, I'd also consider offering a simple/typical name/value > query interface to let users who are most comfortable with using plain > name/value pairs to use them as usual - but also offer a more enhanced > FIQL-powered interface - I guess this flexibility can be supported without too > much extra complexity, with a single Search service only... > > Thanks, Sergey > > > I also agree with targeting this change to 1.3.0. > > > > Regards. > > > >> [1] > >> > https://cwiki.apache.org/confluence/display/SYNCOPE/REST+API+upgrade# > >> RESTAPIupgrade-ConfigurationService > >> > >> [2] http://cxf.apache.org/docs/jax-rs-search.html > > [3] http://tools.ietf.org/html/draft-nottingham-atompub-fiql-00 > >
[jira] [Commented] (SYNCOPE-299) Add "row to display" selector in resources
[ https://issues.apache.org/jira/browse/SYNCOPE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566381#comment-13566381 ] Colm O hEigeartaigh commented on SYNCOPE-299: - The functionality to display the row count is already there - but it relies on an authorization check for a "RESOURCE_LIST" entitlement which is not present. Colm. > Add "row to display" selector in resources > -- > > Key: SYNCOPE-299 > URL: https://issues.apache.org/jira/browse/SYNCOPE-299 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 1.0.5 >Reporter: Denis Signoretto >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.6, 1.1.0 > > > Allow resources list to display more than 10 resources per page (add the > "Rows to display" pager) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-299) Add "row to display" selector in resources
[ https://issues.apache.org/jira/browse/SYNCOPE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566382#comment-13566382 ] Francesco Chicchiriccò commented on SYNCOPE-299: Nice catch! The RESOURCE_LIST entitlement was removed for allowing Self-Registration. (side note: this should be improved as for SYNCOPE-132) For the moment it is safe to remove the authorization check. > Add "row to display" selector in resources > -- > > Key: SYNCOPE-299 > URL: https://issues.apache.org/jira/browse/SYNCOPE-299 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 1.0.5 >Reporter: Denis Signoretto >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.6, 1.1.0 > > > Allow resources list to display more than 10 resources per page (add the > "Rows to display" pager) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (SYNCOPE-301) Status is not updated when synchronizing existing users
Francesco Chicchiriccò created SYNCOPE-301: -- Summary: Status is not updated when synchronizing existing users Key: SYNCOPE-301 URL: https://issues.apache.org/jira/browse/SYNCOPE-301 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.5, 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.0.6, 1.1.0 Even though the flag "Synchronize user status" is checked on the SyncTask, the status (enabled / disabled) on the synchronizing external resources does not make any suspend() / reactivate() to take place on Syncope, for existing users. For non-existing users, however, everything is working as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-299) Add "row to display" selector in resources
[ https://issues.apache.org/jira/browse/SYNCOPE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566389#comment-13566389 ] Colm O hEigeartaigh commented on SYNCOPE-299: - Thanks Francesco! Should the authz check also be removed on 1.0.x? Colm. > Add "row to display" selector in resources > -- > > Key: SYNCOPE-299 > URL: https://issues.apache.org/jira/browse/SYNCOPE-299 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 1.0.5 >Reporter: Denis Signoretto >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.6, 1.1.0 > > > Allow resources list to display more than 10 resources per page (add the > "Rows to display" pager) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SYNCOPE-122) Password change on an external resource only
[ https://issues.apache.org/jira/browse/SYNCOPE-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-122. Resolution: Fixed http://svn.apache.org/viewvc?rev=1440351&view=rev > Password change on an external resource only > > > Key: SYNCOPE-122 > URL: https://issues.apache.org/jira/browse/SYNCOPE-122 > Project: Syncope > Issue Type: New Feature >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 1.1.0 > > > Give option to change password only on one or more connected external > resources; currently it's only possible to change password on Syncope core > and then propagate accordingly to the connected external resources. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-299) Add "row to display" selector in resources
[ https://issues.apache.org/jira/browse/SYNCOPE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566391#comment-13566391 ] Francesco Chicchiriccò commented on SYNCOPE-299: Yes, please. Thanks! > Add "row to display" selector in resources > -- > > Key: SYNCOPE-299 > URL: https://issues.apache.org/jira/browse/SYNCOPE-299 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 1.0.5 >Reporter: Denis Signoretto >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.6, 1.1.0 > > > Allow resources list to display more than 10 resources per page (add the > "Rows to display" pager) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SYNCOPE-299) Add "row to display" selector in resources
[ https://issues.apache.org/jira/browse/SYNCOPE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved SYNCOPE-299. - Resolution: Fixed > Add "row to display" selector in resources > -- > > Key: SYNCOPE-299 > URL: https://issues.apache.org/jira/browse/SYNCOPE-299 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 1.0.5 >Reporter: Denis Signoretto >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.6, 1.1.0 > > > Allow resources list to display more than 10 resources per page (add the > "Rows to display" pager) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: svn commit: r1439854 - in /syncope/trunk: common/src/main/java/org/apache/syncope/common/to/ console/src/main/java/org/apache/syncope/console/commons/ console/src/main/java/org/apache/syncope/cons
Hi Francesco,
-List choices = new ArrayList(
mapConnBundleTO.get(connectorTO.getBundleName()).keySet());
-version.setChoices(choices);
-if (choices.size() == 1) {
-connectorTO.setVersion(choices.get(0));
-version.getField().setModelObject(choices.get(0));
-
connectorTO.setDisplayName(displayName.getModelObject());
-bundleTO = getSelectedBundleTO(mapConnBundleTO,
connectorTO);
-properties = fillProperties(bundleTO, connectorTO);
-}
+version.setChoices(new
ArrayList(mapConnBundleTO.get(connectorTO.getBundleName()).keySet()));
Was this change intended? It reverted the merge I did to select a single
version number by default.
Colm.
On Tue, Jan 29, 2013 at 12:24 PM, wrote:
> Author: ilgrosso
> Date: Tue Jan 29 12:24:34 2013
> New Revision: 1439854
>
> URL: http://svn.apache.org/viewvc?rev=1439854&view=rev
> Log:
> [SYNCOPE-122] Extension on console almost done: only missing on-the-fly
> selection for resources added (directly or via role selection) but not yet
> submitted
>
> Added:
> syncope/trunk/console/src/main/webapp/img/actions/enable.png (with
> props)
> Modified:
>
> syncope/trunk/common/src/main/java/org/apache/syncope/common/to/PropagationRequestTO.java
>
> syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/StatusBean.java
>
> syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/StatusUtils.java
>
> syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/ConnectorModalPage.java
>
> syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/EditUserModalPage.java
>
> syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/UserModalPage.java
>
> syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/AbstractSearchResultPanel.java
>
> syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/StatusPanel.java
>
> syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/UserSearchResultPanel.java
>
> syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/UserRestClient.java
>
> syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/markup/html/form/ActionLink.java
>
> syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/markup/html/form/ActionLinksPanel.java
>
> syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/ResultStatusModalPage.html
>
> syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/UserModalPage.html
>
> syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/UserModalPage.properties
>
> syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/UserModalPage_it.properties
>
> syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/panels/StatusPanel.html
>
> syncope/trunk/console/src/main/resources/org/apache/syncope/console/wicket/markup/html/form/ActionLinksPanel.html
>
> syncope/trunk/console/src/test/java/org/apache/syncope/console/ConfigurationTestITCase.java
>
> syncope/trunk/console/src/test/java/org/apache/syncope/console/ConnInstanceTestITCase.java
>
> syncope/trunk/console/src/test/java/org/apache/syncope/console/ReportTestITCase.java
>
> syncope/trunk/console/src/test/java/org/apache/syncope/console/ResourceTestITCase.java
>
> syncope/trunk/console/src/test/java/org/apache/syncope/console/RoleTestITCase.java
>
> syncope/trunk/console/src/test/java/org/apache/syncope/console/SchemaTestITCase.java
>
> syncope/trunk/console/src/test/java/org/apache/syncope/console/TaskTestITCase.java
>
> syncope/trunk/console/src/test/java/org/apache/syncope/console/UserTestITCase.java
>
> Modified:
> syncope/trunk/common/src/main/java/org/apache/syncope/common/to/PropagationRequestTO.java
> URL:
> http://svn.apache.org/viewvc/syncope/trunk/common/src/main/java/org/apache/syncope/common/to/PropagationRequestTO.java?rev=1439854&r1=1439853&r2=1439854&view=diff
>
> ==
> ---
> syncope/trunk/common/src/main/java/org/apache/syncope/common/to/PropagationRequestTO.java
> (original)
> +++
> syncope/trunk/common/src/main/java/org/apache/syncope/common/to/PropagationRequestTO.java
> Tue Jan 29 12:24:34 2013
> @@ -20,12 +20,10 @@ package org.apache.syncope.common.to;
>
> import java.util.HashSet;
> import java.util.Set;
> -
> import javax.xml.bind.annotation.XmlElement;
> import javax.xml.bind.annotation.XmlElementWrapper;
> import javax.xml.bind.annotation.XmlRootElement;
> import javax.xml.bind.annotation.XmlType;
> -
> import org.apache.syncope.common.AbstractBaseBean;
>
> /**
>
> Modified:
> syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/StatusBean.java
> URL:
> http://svn.apache.org/viewvc/syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/Statu
Re: svn commit: r1439854 - in /syncope/trunk: common/src/main/java/org/apache/syncope/common/to/ console/src/main/java/org/apache/syncope/console/commons/ console/src/main/java/org/apache/syncope/cons
On 30/01/2013 12:56, Colm O hEigeartaigh wrote:
Hi Francesco,
-List choices = new ArrayList(
mapConnBundleTO.get(connectorTO.getBundleName()).keySet());
-version.setChoices(choices);
-if (choices.size() == 1) {
-connectorTO.setVersion(choices.get(0));
-version.getField().setModelObject(choices.get(0));
-
connectorTO.setDisplayName(displayName.getModelObject());
-bundleTO = getSelectedBundleTO(mapConnBundleTO,
connectorTO);
-properties = fillProperties(bundleTO, connectorTO);
-}
+version.setChoices(new
ArrayList(mapConnBundleTO.get(connectorTO.getBundleName()).keySet()));
Was this change intended? It reverted the merge I did to select a single
version number by default.
Sorry Colm, my mistake: yesterday I played a bit hard with SVN merge to
cope with SYNCOPE-293 and I thus have involuntarily reverted your commit
as well.
Would you like me to fix this or do you already have the fix ready?
Regards.
--
Francesco Chicchiriccò
ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
Re: svn commit: r1439854 - in /syncope/trunk: common/src/main/java/org/apache/syncope/common/to/ console/src/main/java/org/apache/syncope/console/commons/ console/src/main/java/org/apache/syncope/cons
> Sorry Colm, my mistake: yesterday I played a bit hard with SVN merge to
cope with SYNCOPE-293 and I thus have involuntarily
> reverted your commit as well.
No problem.
> Would you like me to fix this or do you already have the fix ready?
If you could do it that'd be great - just make sure no other commit was
overwritten I guess!
Thanks,
Colm.
On Wed, Jan 30, 2013 at 12:11 PM, Francesco Chicchiriccò <
ilgro...@apache.org> wrote:
> On 30/01/2013 12:56, Colm O hEigeartaigh wrote:
>
>> Hi Francesco,
>>
>> -List choices = new ArrayList(
>> mapConnBundleTO.get(**connectorTO.getBundleName()).**keySet());
>> -version.setChoices(choices);
>> -if (choices.size() == 1) {
>> -connectorTO.setVersion(**choices.get(0));
>> -version.getField().**setModelObject(choices.get(0))*
>> *;
>> -
>> connectorTO.setDisplayName(**displayName.getModelObject());
>> -bundleTO = getSelectedBundleTO(**mapConnBundleTO,
>> connectorTO);
>> -properties = fillProperties(bundleTO, connectorTO);
>> -}
>> +version.setChoices(new
>> ArrayList(**mapConnBundleTO.get(**connectorTO.getBundleName()).**
>> keySet()));
>>
>> Was this change intended? It reverted the merge I did to select a single
>> version number by default.
>>
>
> Sorry Colm, my mistake: yesterday I played a bit hard with SVN merge to
> cope with SYNCOPE-293 and I thus have involuntarily reverted your commit as
> well.
>
> Would you like me to fix this or do you already have the fix ready?
>
> Regards.
>
> --
> Francesco Chicchiriccò
>
> ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
> http://people.apache.org/~**ilgrosso/
Re: Discuss: Move InvalidSearchConditionException to common
Hi Francesco, I am currently working on the patch to move the InvalidSearchConditionException and make it checked again. I am not sure if making it checked is a good idea. As the exception will now be part of the service interface I will have to add it to lots of methods. None of these methods really handles this exception. The reason for this is that before we used the RestTemplate to access the services. So it did not matter if the service throws a checked exception. We would not be forced to catch it. Now with the interfaces for the services we have to add the checked exception to the service interface if we want the impl to be able to throw it. So the client is also affected by that. In the end the exception now also appears in AttributableDataProvider which can not rethrow the exception as it would violate the IDataProvider interface. So I would have to catch it there but I have no idea what to do if it happens. I created a gist of the patch so you can have a look: https://gist.github.com/4672932 So I see two possible solutions to improve this: 1) Make the exception unchecked again so it can be thrown by the services but has no effect on the client side 2) Catch the exception in the server impls and rethrow it as a RuntimeException so it does not affect the clients What do you think? Christian On 30.01.2013 08:29, Francesco Chicchiriccò wrote: > On 28/01/2013 15:38, Francesco Chicchiriccò wrote: >> On 28/01/2013 15:36, Christian Schneider wrote: >>> Currently InvalidSearchConditionException is in core.persistence.dao >>> and >>> is a checked exception. >>> If we want to make this exception part of the UserService interface to >>> have it available on the client we will have to move it to common. >>> >>> Currently the console does not seem to use the exception on the client >>> side. So my preliminary solution to get it running is to make the >>> exception unchecked so I can pass it to the >>> exception mapper without having it in the interface. >>> >>> So basically the two things to discuss are if we want to move the >>> exception to common and if we want to make it unchecked. I personally >>> would do both. >> >> This exception is not used by the admin console because the code is >> done so that no invalid search conditions are sent to the core; >> however, other clients are likely to need this exception to be returned. >> >> Hence: +1 for moving it to common, but don't see enough reason to >> make it unchecked. > > I've noticed that this issue was moved to common as unchecked: any > additional reason behind not leaving it checked than the need to > change some interface method's signature? > > Regards. > -- Christian Schneider http://www.liquid-reality.de Open Source Architect http://www.talend.com
[jira] [Commented] (SYNCOPE-299) Add "row to display" selector in resources
[ https://issues.apache.org/jira/browse/SYNCOPE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566421#comment-13566421 ] Hudson commented on SYNCOPE-299: Integrated in Syncope-1_0_X #125 (See [https://builds.apache.org/job/Syncope-1_0_X/125/]) [SYNCOPE-299] - Backmerged. (Revision 1440355) Result = SUCCESS coheigea : Files : * /syncope/branches/1_0_X * /syncope/branches/1_0_X/console/src/main/java/org/apache/syncope/console/commons/XMLRolesReader.java * /syncope/branches/1_0_X/console/src/main/java/org/apache/syncope/console/pages/Resources.java > Add "row to display" selector in resources > -- > > Key: SYNCOPE-299 > URL: https://issues.apache.org/jira/browse/SYNCOPE-299 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 1.0.5 >Reporter: Denis Signoretto >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.6, 1.1.0 > > > Allow resources list to display more than 10 resources per page (add the > "Rows to display" pager) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
RE: Build not working (again) with JDK 1.7
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) Time elapsed: 0.172 sec <<< ERROR!
org.apache.syncope.common.validation.SyncopeClientCompositeErrorException: {[Dat
aIntegrityViolation [The transaction has been rolled back. See the nested excep
tions for details on the errors that occurred.]]}
This problem is really related to SYNCOPE-298:
SEVERE: Servlet.service() for servlet [syncope-core-rest] in context with path
[/syncope] threw exception [Request processing failed; nested exception is
org.springframework.dao.DataIntegrityViolationException: The transaction has
been rolled back. See the nested exceptions for details on the errors that
occurred.; nested exception is org.apache.openjpa.persistence.EntityExistsException: The transaction
has been rolled back. See the nested exceptions for details on the errors that
occurred.
FailedObject: org.apache.syncope.core.persistence.beans.user.UVirAttr@3aa73b72]
with root cause
org.apache.openjpa.lib.jdbc.ReportingSQLException: Unique index or primary key
violation: "PRIMARY_KEY_C4 ON PUBLIC.UVIRATTR(ID)"; SQL statement:
INSERT INTO PUBLIC.UVirAttr (ID, OWNER_ID, VIRTUALSCHEMA_NAME) VALUES (?, ?, ?)
[23505-170] {prepstmnt 178787393 INSERT INTO PUBLIC.UVirAttr (ID, OWNER_ID,
VIRTUALSCHEMA_NAME) VALUES (?, ?, ?)} [code=23505, state=23505]
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219)
at
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:195)
Could you please experiment a little bit in your environment:
1. Check cargo-output.log for
org.apache.openjpa.persistence.EntityExistsException related to
org.apache.syncope.core.persistence.beans.user.UVirAttr
2. Run UserTestITCase and TaskITTestCase separately and check if problems are
still there.
?
Let see if it will be necessary to re-prioritize SYNCOPE-298.
Regards,
Andrei.
P.S: Task patch from SYNCOPE-231 has inserted @Ignored to 2 TaskTestITCase
tests. I will care to enable them again.
> -Original Message-
> From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
> Sent: Mittwoch, 30. Januar 2013 11:41
> To: dev@syncope.apache.org
> Subject: Build not working (again) with JDK 1.7
>
> Hi all,
> unfortunately, after latest updates since yesterday afternoon when I did my
> last checks, the build on JDK 1.7 is failing again:
>
> Results :
>
> Failed tests:
>UserTestITCase.create:481 expected:<166> but was:<165>
>UserTestITCase.verifyTaskRegistration:1000 expected:<187> but was:<186>
>
> Tests in error:
>TaskTestITCase.sync:325 » SyncopeClientCompositeError {[NotFound [User
> test0]]...
>
>
> With JDK 1.6 no problems (as Jenkins confirms).
>
> Both behaviours seems to be stable.
>
> Andrei told me yesterday that this is not the case, but just for sake of
> completeness, let's think again if this is related to SYNCOPE-298.
>
> If not, what can be the reason of these failures with JDK 1.7?
>
> Regards.
>
> --
> Francesco Chicchiriccò
>
> ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
> http://people.apache.org/~ilgrosso/
Re: svn commit: r1439854 - in /syncope/trunk: common/src/main/java/org/apache/syncope/common/to/ console/src/main/java/org/apache/syncope/console/commons/ console/src/main/java/org/apache/syncope/cons
On 30/01/2013 13:19, Colm O hEigeartaigh wrote: Would you like me to fix this or do you already have the fix ready? If you could do it that'd be great - just make sure no other commit was overwritten I guess! Done; that should be the only one. Regards. -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
[jira] [Commented] (SYNCOPE-299) Add "row to display" selector in resources
[ https://issues.apache.org/jira/browse/SYNCOPE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566446#comment-13566446 ] Hudson commented on SYNCOPE-299: Integrated in Syncope-trunk #32 (See [https://builds.apache.org/job/Syncope-trunk/32/]) [SYNCOPE-299] - Add "row to display" selector in resources - Removing authorization check for a entitlement (resource_list) that no longer exists (Revision 1440353) Result = SUCCESS coheigea : Files : * /syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/XMLRolesReader.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/Resources.java > Add "row to display" selector in resources > -- > > Key: SYNCOPE-299 > URL: https://issues.apache.org/jira/browse/SYNCOPE-299 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 1.0.5 >Reporter: Denis Signoretto >Assignee: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.0.6, 1.1.0 > > > Allow resources list to display more than 10 resources per page (add the > "Rows to display" pager) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-231) Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack)
[ https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566447#comment-13566447 ] Hudson commented on SYNCOPE-231: Integrated in Syncope-trunk #32 (See [https://builds.apache.org/job/Syncope-trunk/32/]) SYNCOPE-231 Switching ReportTO to use AbstractReportletConf to enable JAXB serialization (Revision 1440358) Result = SUCCESS cschneider : Files : * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/ReportTO.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/ReportModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/ReportletConfModalPage.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/data/ReportDataBinder.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/ReportTestITCase.java > Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack) > -- > > Key: SYNCOPE-231 > URL: https://issues.apache.org/jira/browse/SYNCOPE-231 > Project: Syncope > Issue Type: Improvement > Components: console, core >Reporter: Jan Bernhardt >Assignee: Jan Bernhardt > Fix For: 1.1.0 > > Attachments: TaskService.patch > > > Current REST Interfaces are based on Spring Webservice framework. > Goal of this task is to replace Spring with CXF and to relay on JAX-B and > JAX-RS annotations rather then Spring annotations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-122) Password change on an external resource only
[ https://issues.apache.org/jira/browse/SYNCOPE-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566448#comment-13566448 ] Hudson commented on SYNCOPE-122: Integrated in Syncope-trunk #32 (See [https://builds.apache.org/job/Syncope-trunk/32/]) [SYNCOPE-122] Console extension completed featuring on-the-fly selection for resources added (directly or via role selection) but not yet submitted (Revision 1440351) Result = SUCCESS ilgrosso : Files : * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/AbstractAttributableTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/UserTO.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/RoleTreeBuilder.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/RoleUtils.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/SelectChoiceRenderer.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/StatusUtils.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/markup/html/CrontabContainer.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/EditUserModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/MembershipModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/UserModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/DerivedAttributesPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/MembershipsPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/ResourcesPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/StatusPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/markup/html/form/AbstractFieldPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/markup/html/form/AjaxPalettePanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/markup/html/tree/TreeRoleProvider.java * /syncope/trunk/console/src/test/java/org/apache/syncope/console/EditProfileTestITCase.java > Password change on an external resource only > > > Key: SYNCOPE-122 > URL: https://issues.apache.org/jira/browse/SYNCOPE-122 > Project: Syncope > Issue Type: New Feature >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 1.1.0 > > > Give option to change password only on one or more connected external > resources; currently it's only possible to change password on Syncope core > and then propagate accordingly to the connected external resources. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (SYNCOPE-297) External Attributes are showing up for AccoundId/Password in Resource User Mappings
[ https://issues.apache.org/jira/browse/SYNCOPE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh reassigned SYNCOPE-297: --- Assignee: Colm O hEigeartaigh > External Attributes are showing up for AccoundId/Password in Resource User > Mappings > --- > > Key: SYNCOPE-297 > URL: https://issues.apache.org/jira/browse/SYNCOPE-297 > Project: Syncope > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 1.1.0 > > Attachments: Screenshot.png > > > I have a Database Connector for a H2 backend with a simple table. I am > creating a Resource User Mapping of Username -> Account Id, Password -> > Password, and a User schema 'surname' attribute -> SURNAME column in the > table. > The Resource now creates ok, however when I edit it and look at the User > mappings, I see that another column name 'GIVENNAME' is appearing as the > external attribute for the User Account Id and Password mappings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-297) External Attributes are showing up for AccoundId/Password in Resource User Mappings
[ https://issues.apache.org/jira/browse/SYNCOPE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566459#comment-13566459 ] Colm O hEigeartaigh commented on SYNCOPE-297: - Hi Jan, Could you elaborate on what exception you are getting? I am not seeing an exception there. I believe the problem is due to the functionality added in MappingTO on trunk. A AccountId MappingItemTO object has an external attribute name of "__NAME__" and "__PASSWORD__" for a Password object. On 1.0.x they just have "null". This appears to be confusing the Wicket DropdownChoice, as it is getting initialized with a value that does not correspond to the choices (GIVENNAME + SURNAME) in this case. Questions: A) Should MappingItemTO have defined external attribute names added for AccountID/Passwords? B) If the answer to (A) is yes, then I can just remove the external attribute choices for AccountID/Password mappings. Colm. > External Attributes are showing up for AccoundId/Password in Resource User > Mappings > --- > > Key: SYNCOPE-297 > URL: https://issues.apache.org/jira/browse/SYNCOPE-297 > Project: Syncope > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 1.1.0 > > Attachments: Screenshot.png > > > I have a Database Connector for a H2 backend with a simple table. I am > creating a Resource User Mapping of Username -> Account Id, Password -> > Password, and a User schema 'surname' attribute -> SURNAME column in the > table. > The Resource now creates ok, however when I edit it and look at the User > mappings, I see that another column name 'GIVENNAME' is appearing as the > external attribute for the User Account Id and Password mappings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-297) External Attributes are showing up for AccoundId/Password in Resource User Mappings
[ https://issues.apache.org/jira/browse/SYNCOPE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566469#comment-13566469 ] Francesco Chicchiriccò commented on SYNCOPE-297: Hi Colm, MappingItemTO (as its counterpart MappingItem) is used by either user mapping (UMappingTO / UMapping) and role mapping (RMappingTO / RMapping), the latter clearly not having any password mapping item, only accountid. Please consider that both UMapping and RMapping (via their parent AbstractMapping) will force the extAttrName to be Uid.NAME (i.e. "__NAME__") or OperationalAttributes.PASSWORD_NAME (i.e. "__PASSWORD__") despite of the value contained in the correspondent TO. Having said that, I don't understand exactly what you mean with your question (A); however, IMO you can just proceed with (B). > External Attributes are showing up for AccoundId/Password in Resource User > Mappings > --- > > Key: SYNCOPE-297 > URL: https://issues.apache.org/jira/browse/SYNCOPE-297 > Project: Syncope > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 1.1.0 > > Attachments: Screenshot.png > > > I have a Database Connector for a H2 backend with a simple table. I am > creating a Resource User Mapping of Username -> Account Id, Password -> > Password, and a User schema 'surname' attribute -> SURNAME column in the > table. > The Resource now creates ok, however when I edit it and look at the User > mappings, I see that another column name 'GIVENNAME' is appearing as the > external attribute for the User Account Id and Password mappings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-297) External Attributes are showing up for AccoundId/Password in Resource User Mappings
[ https://issues.apache.org/jira/browse/SYNCOPE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566480#comment-13566480 ] Jan Bernhardt commented on SYNCOPE-297: --- Hi Colm, when I was trying to reconstruct your issue, I discovered this error. Here is what I did to run into this error: Build syncope from trunk. Start standalone version. Login as admin. Create new resource with predefined H2 connector. Setup some basic UserSchemaMapping. Saved Resource. Reopened created resource and took a look at UserSchemaMappings. I changed port configuration from my console to 9081 so that I could monitor network traffic. Here I discovered "null" as a response for "/rest/connector/schema/list?showall=true" when handling H2 connections. By analyzing "null" response, I discovered previously mentioned error. I also tried another connector with normal results for "/rest/connector/schema/list?showall=true". Best regards. Jan > External Attributes are showing up for AccoundId/Password in Resource User > Mappings > --- > > Key: SYNCOPE-297 > URL: https://issues.apache.org/jira/browse/SYNCOPE-297 > Project: Syncope > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 1.1.0 > > Attachments: Screenshot.png > > > I have a Database Connector for a H2 backend with a simple table. I am > creating a Resource User Mapping of Username -> Account Id, Password -> > Password, and a User schema 'surname' attribute -> SURNAME column in the > table. > The Resource now creates ok, however when I edit it and look at the User > mappings, I see that another column name 'GIVENNAME' is appearing as the > external attribute for the User Account Id and Password mappings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-81) NotificationTasks cannot be deleted
[
https://issues.apache.org/jira/browse/SYNCOPE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566492#comment-13566492
]
Hudson commented on SYNCOPE-81:
---
Integrated in Syncope-trunk #33 (See
[https://builds.apache.org/job/Syncope-trunk/33/])
[SYNCOPE-231] Enabled Task.SYNCOPE-81 test (Revision 1440405)
Result = SUCCESS
ashakirin :
Files :
*
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/TaskTestITCase.java
> NotificationTasks cannot be deleted
> ---
>
> Key: SYNCOPE-81
> URL: https://issues.apache.org/jira/browse/SYNCOPE-81
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 1.0.0-incubating
>Reporter: fabio martelli
>Assignee: fabio martelli
> Fix For: 1.0.0-incubating
>
>
> NotificationTasks cannot be deleted:
> Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: Referential
> integrity constraint violation: "CONSTRAINT_163: PUBLIC.TASKEXEC FOREIGN
> KEY(TASK_ID) REFERENCES PUBLIC.TASK(ID) (11)"; SQL statement:
> DELETE FROM PUBLIC.Task WHERE ID = ? [23503-166] {prepstmnt 1884954755 DELETE
> FROM PUBLIC.Task WHERE ID = ? [params=?]} [code=23503, state=23503]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-231) Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack)
[ https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566491#comment-13566491 ] Hudson commented on SYNCOPE-231: Integrated in Syncope-trunk #33 (See [https://builds.apache.org/job/Syncope-trunk/33/]) [SYNCOPE-231] * adding JAVA DOC * renaming validate to check for connector service * Code cleanup (Revision 1440409) [SYNCOPE-231] Enabled Task.SYNCOPE-81 test (Revision 1440405) Result = SUCCESS jbernhardt : Files : * /syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/ConnectorServiceProxy.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/SyncopeConstants.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/ConfigurationService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/ConnectorService.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/ConnectorRestClient.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/ConnectorServiceImpl.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/ConnInstanceTestITCase.java ashakirin : Files : * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/TaskTestITCase.java > Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack) > -- > > Key: SYNCOPE-231 > URL: https://issues.apache.org/jira/browse/SYNCOPE-231 > Project: Syncope > Issue Type: Improvement > Components: console, core >Reporter: Jan Bernhardt >Assignee: Jan Bernhardt > Fix For: 1.1.0 > > Attachments: TaskService.patch > > > Current REST Interfaces are based on Spring Webservice framework. > Goal of this task is to replace Spring with CXF and to relay on JAX-B and > JAX-RS annotations rather then Spring annotations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-297) External Attributes are showing up for AccoundId/Password in Resource User Mappings
[
https://issues.apache.org/jira/browse/SYNCOPE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566510#comment-13566510
]
Colm O hEigeartaigh commented on SYNCOPE-297:
-
Hi Francesco,
>> A) Should MappingItemTO have defined external attribute names added for
>> AccountID/Passwords?
> Having said that, I don't understand exactly what you mean with your question
> (A); however, IMO you can just proceed with (B).
What I meant was that the 'addAccountIdItem' method here:
http://svn.apache.org/viewvc/syncope/trunk/common/src/main/java/org/apache/syncope/common/to/MappingTO.java?view=markup
is explicitly setting "accountIdItem.setExtAttrName("__NAME__");" (and similar
for the Password case). I was wondering whether it should be doing this, as on
1.0.x the corresponding getExtAttrName() for the AccountId Mapping returns
null. If I set the above call to null then all of the tests pass.
Colm.
> External Attributes are showing up for AccoundId/Password in Resource User
> Mappings
> ---
>
> Key: SYNCOPE-297
> URL: https://issues.apache.org/jira/browse/SYNCOPE-297
> Project: Syncope
> Issue Type: Bug
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
> Fix For: 1.1.0
>
> Attachments: Screenshot.png
>
>
> I have a Database Connector for a H2 backend with a simple table. I am
> creating a Resource User Mapping of Username -> Account Id, Password ->
> Password, and a User schema 'surname' attribute -> SURNAME column in the
> table.
> The Resource now creates ok, however when I edit it and look at the User
> mappings, I see that another column name 'GIVENNAME' is appearing as the
> external attribute for the User Account Id and Password mappings.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (SYNCOPE-297) External Attributes are showing up for AccoundId/Password in Resource User Mappings
[ https://issues.apache.org/jira/browse/SYNCOPE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566513#comment-13566513 ] Francesco Chicchiriccò edited comment on SYNCOPE-297 at 1/30/13 2:36 PM: - Provided that, as I say above, the value of MappingItemTO.extAttrName is ignored by core for AccountId and Password items, why not setting both values to null (as in 1_0_X) from the admin console? was (Author: ilgrosso): Provided that, as I say above, the value of MappingItemTO.extAttrName is ignored by core for AccountId and Password items, why not setting both to values to null (as in 1_0_X) from the admin console? > External Attributes are showing up for AccoundId/Password in Resource User > Mappings > --- > > Key: SYNCOPE-297 > URL: https://issues.apache.org/jira/browse/SYNCOPE-297 > Project: Syncope > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 1.1.0 > > Attachments: Screenshot.png > > > I have a Database Connector for a H2 backend with a simple table. I am > creating a Resource User Mapping of Username -> Account Id, Password -> > Password, and a User schema 'surname' attribute -> SURNAME column in the > table. > The Resource now creates ok, however when I edit it and look at the User > mappings, I see that another column name 'GIVENNAME' is appearing as the > external attribute for the User Account Id and Password mappings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-297) External Attributes are showing up for AccoundId/Password in Resource User Mappings
[ https://issues.apache.org/jira/browse/SYNCOPE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566513#comment-13566513 ] Francesco Chicchiriccò commented on SYNCOPE-297: Provided that, as I say above, the value of MappingItemTO.extAttrName is ignored by core for AccountId and Password items, why not setting both to values to null (as in 1_0_X) from the admin console? > External Attributes are showing up for AccoundId/Password in Resource User > Mappings > --- > > Key: SYNCOPE-297 > URL: https://issues.apache.org/jira/browse/SYNCOPE-297 > Project: Syncope > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh > Fix For: 1.1.0 > > Attachments: Screenshot.png > > > I have a Database Connector for a H2 backend with a simple table. I am > creating a Resource User Mapping of Username -> Account Id, Password -> > Password, and a User schema 'surname' attribute -> SURNAME column in the > table. > The Resource now creates ok, however when I edit it and look at the User > mappings, I see that another column name 'GIVENNAME' is appearing as the > external attribute for the User Account Id and Password mappings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-231) Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack)
[ https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566519#comment-13566519 ] Hudson commented on SYNCOPE-231: Integrated in Syncope-trunk #34 (See [https://builds.apache.org/job/Syncope-trunk/34/]) [SYNCOPE-231] * adding JAVA DOC for LoggerService * changing response type for update and delete NotificationService methods to void * Code cleanup (Revision 1440427) Result = SUCCESS jbernhardt : Files : * /syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/NotificationServiceProxy.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/LoggerService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/NotificationService.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/NotificationRestClient.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/ConnInstanceController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/NotificationServiceImpl.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/NotificationTestITCase.java > Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack) > -- > > Key: SYNCOPE-231 > URL: https://issues.apache.org/jira/browse/SYNCOPE-231 > Project: Syncope > Issue Type: Improvement > Components: console, core >Reporter: Jan Bernhardt >Assignee: Jan Bernhardt > Fix For: 1.1.0 > > Attachments: TaskService.patch > > > Current REST Interfaces are based on Spring Webservice framework. > Goal of this task is to replace Spring with CXF and to relay on JAX-B and > JAX-RS annotations rather then Spring annotations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-231) Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack)
[ https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566550#comment-13566550 ] Hudson commented on SYNCOPE-231: Integrated in Syncope-trunk #35 (See [https://builds.apache.org/job/Syncope-trunk/35/]) SYNCOPE-231 Handling client side exceptions in SchemaService create (Revision 1440464) SYNCOPE-231 Fix error in cxf authentication (Revision 1440441) Result = SUCCESS cschneider : Files : * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AbstractTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AuthenticationTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/DerivedSchemaTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/SchemaTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/VirtualSchemaTestITCase.java cschneider : Files : * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AbstractTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AuthenticationTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/RoleTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/SearchTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/TaskTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserRequestTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java > Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack) > -- > > Key: SYNCOPE-231 > URL: https://issues.apache.org/jira/browse/SYNCOPE-231 > Project: Syncope > Issue Type: Improvement > Components: console, core >Reporter: Jan Bernhardt >Assignee: Jan Bernhardt > Fix For: 1.1.0 > > Attachments: TaskService.patch > > > Current REST Interfaces are based on Spring Webservice framework. > Goal of this task is to replace Spring with CXF and to relay on JAX-B and > JAX-RS annotations rather then Spring annotations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-298) Persistence beans: change AUTO Id generation strategy to TABLE
[ 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 could not be AUTO generation strategy itself, but collision with pre-configured attributes in content.xml. As far as AUTO generation strategy cannot limit Ids interval, generated Ids can be intersected with pre-configured. It requires additional analyses. > Persistence beans: change AUTO Id generation strategy to TABLE > -- > > Key: SYNCOPE-298 > URL: https://issues.apache.org/jira/browse/SYNCOPE-298 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Andrei Shakirin > Fix For: 1.2.0 > > > Currently AUTO Id generation strategy works unstable under high > load/concurrency conditions at least for H2 DB. [1], [2] > Possible solution of this problem is migration AUTO to TABLE Id generation > strategy for all persistence domain objects. > [1] > http://syncope-dev.1063484.n5.nabble.com/Question-Problem-with-test-UsertTestITCase-issueSYNCOPE279-tt5712389.html > [2] > http://syncope-dev.1063484.n5.nabble.com/Persistence-id-generation-strategy-TABLE-vs-AUTO-td5711813.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-301) Status is not updated when synchronizing existing users
[ https://issues.apache.org/jira/browse/SYNCOPE-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566605#comment-13566605 ] Francesco Chicchiriccò commented on SYNCOPE-301: Fir for 1_0_X: http://svn.apache.org/viewvc?rev=1440512&view=rev > Status is not updated when synchronizing existing users > --- > > Key: SYNCOPE-301 > URL: https://issues.apache.org/jira/browse/SYNCOPE-301 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.0.5, 1.1.0 >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 1.0.6, 1.1.0 > > > Even though the flag "Synchronize user status" is checked on the SyncTask, > the status (enabled / disabled) on the synchronizing external resources does > not make any suspend() / reactivate() to take place on Syncope, for existing > users. > For non-existing users, however, everything is working as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (SYNCOPE-301) Status is not updated when synchronizing existing users
[ https://issues.apache.org/jira/browse/SYNCOPE-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566605#comment-13566605 ] Francesco Chicchiriccò edited comment on SYNCOPE-301 at 1/30/13 4:45 PM: - Fix for 1_0_X: http://svn.apache.org/viewvc?rev=1440512&view=rev was (Author: ilgrosso): Fir for 1_0_X: http://svn.apache.org/viewvc?rev=1440512&view=rev > Status is not updated when synchronizing existing users > --- > > Key: SYNCOPE-301 > URL: https://issues.apache.org/jira/browse/SYNCOPE-301 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.0.5, 1.1.0 >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 1.0.6, 1.1.0 > > > Even though the flag "Synchronize user status" is checked on the SyncTask, > the status (enabled / disabled) on the synchronizing external resources does > not make any suspend() / reactivate() to take place on Syncope, for existing > users. > For non-existing users, however, everything is working as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SYNCOPE-301) Status is not updated when synchronizing existing users
[ https://issues.apache.org/jira/browse/SYNCOPE-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-301. Resolution: Fixed Fix for trunk: http://svn.apache.org/viewvc?rev=1440561&view=rev > Status is not updated when synchronizing existing users > --- > > Key: SYNCOPE-301 > URL: https://issues.apache.org/jira/browse/SYNCOPE-301 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.0.5, 1.1.0 >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 1.0.6, 1.1.0 > > > Even though the flag "Synchronize user status" is checked on the SyncTask, > the status (enabled / disabled) on the synchronizing external resources does > not make any suspend() / reactivate() to take place on Syncope, for existing > users. > For non-existing users, however, everything is working as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SYNCOPE-210) Provide suggestions / help / examples for JEXL-based input fields
[ https://issues.apache.org/jira/browse/SYNCOPE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimiliano Perrone updated SYNCOPE-210: - Attachment: one.png two.png Hi guys, after different tests, this is, IMHO, the better solution to resolve issue. 1) No JavaScript, only wicket stuff. 2) Clicking on question mark the label shows/hides Layout is still working progress. > Provide suggestions / help / examples for JEXL-based input fields > - > > Key: SYNCOPE-210 > URL: https://issues.apache.org/jira/browse/SYNCOPE-210 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Francesco Chicchiriccò >Assignee: Massimiliano Perrone > Fix For: 1.1.0 > > Attachments: one.png, two.png > > > There are many input text fields accepting JEXL syntax: > * derived schema definition (user / role / membership) > * values for defining synchronization user template > * schema mapping's mandatory condition > * ... > Users would benefit from some examples, help, suggestions, link to JEXL > reference to be displayed in (or linked from) the web forms containing such > input fields. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-301) Status is not updated when synchronizing existing users
[ https://issues.apache.org/jira/browse/SYNCOPE-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566730#comment-13566730 ] Hudson commented on SYNCOPE-301: Integrated in Syncope-trunk #36 (See [https://builds.apache.org/job/Syncope-trunk/36/]) [SYNCOPE-301] Merge from 1_0_X (Revision 1440561) Result = FAILURE ilgrosso : Files : * /syncope/trunk * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/beans/AbstractBaseBean.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/beans/user/SyncopeUser.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/security/SyncopeAuthenticationProvider.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/sync/impl/SyncopeSyncResultHandler.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/WorkflowResult.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/user/NoOpUserWorkflowAdapter.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/TaskTestITCase.java * /syncope/trunk/core/src/test/resources/content.xml > Status is not updated when synchronizing existing users > --- > > Key: SYNCOPE-301 > URL: https://issues.apache.org/jira/browse/SYNCOPE-301 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.0.5, 1.1.0 >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 1.0.6, 1.1.0 > > > Even though the flag "Synchronize user status" is checked on the SyncTask, > the status (enabled / disabled) on the synchronizing external resources does > not make any suspend() / reactivate() to take place on Syncope, for existing > users. > For non-existing users, however, everything is working as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-231) Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack)
[ https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566731#comment-13566731 ] Hudson commented on SYNCOPE-231: Integrated in Syncope-trunk #36 (See [https://builds.apache.org/job/Syncope-trunk/36/]) SYNCOPE-231 Bugfix for delete (Revision 1440563) SYNCOPE-231 Adding AuthenticationTestITCaseJAXRS (Revision 1440562) SYNCOPE-231 Refactored AuthenticationTestITCase (Revision 1440514) [SYNCOPE-231] * adding JAVA DOC for LoggerService * adding fromString method for some enum types * Code cleanup (Revision 1440496) [SYNCOPE-231] Fixed and enabled Task.deal() test (Revision 1440494) Result = FAILURE cschneider : Files : * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/UserRequestServiceImpl.java cschneider : Files : * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/AuthenticationTestITCaseJAXRS.java cschneider : Files : * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AuthenticationTestITCase.java jbernhardt : Files : * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/PolicyService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/ReportService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/CipherAlgorithm.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/ConflictResolutionAction.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/ConnParameterType.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/ConnectorCapability.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/ReportExecExportFormat.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/ResourceOperation.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/TaskType.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/UserRequestType.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/ReportRestClient.java ashakirin : Files : * /syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/TaskServiceProxy.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/TaskTestITCase.java > Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack) > -- > > Key: SYNCOPE-231 > URL: https://issues.apache.org/jira/browse/SYNCOPE-231 > Project: Syncope > Issue Type: Improvement > Components: console, core >Reporter: Jan Bernhardt >Assignee: Jan Bernhardt > Fix For: 1.1.0 > > Attachments: TaskService.patch > > > Current REST Interfaces are based on Spring Webservice framework. > Goal of this task is to replace Spring with CXF and to relay on JAX-B and > JAX-RS annotations rather then Spring annotations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Syncope-trunk - Build # 36 - Failure
The Apache Jenkins build system has built Syncope-trunk (build #36) Status: Failure Check console output at https://builds.apache.org/job/Syncope-trunk/36/ to view the results.
[jira] [Commented] (SYNCOPE-301) Status is not updated when synchronizing existing users
[ https://issues.apache.org/jira/browse/SYNCOPE-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566764#comment-13566764 ] Hudson commented on SYNCOPE-301: Integrated in Syncope-1_0_X #126 (See [https://builds.apache.org/job/Syncope-1_0_X/126/]) [SYNCOPE-301] Fix for branch 1_0_X (Revision 1440512) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_0_X/core/src/main/java/org/apache/syncope/core/persistence/beans/AbstractBaseBean.java * /syncope/branches/1_0_X/core/src/main/java/org/apache/syncope/core/persistence/beans/user/SyncopeUser.java * /syncope/branches/1_0_X/core/src/main/java/org/apache/syncope/core/policy/AccountPolicyEnforcer.java * /syncope/branches/1_0_X/core/src/main/java/org/apache/syncope/core/scheduling/SyncJob.java * /syncope/branches/1_0_X/core/src/main/java/org/apache/syncope/core/security/SyncopeAuthenticationProvider.java * /syncope/branches/1_0_X/core/src/main/java/org/apache/syncope/core/workflow/AbstractUserWorkflowAdapter.java * /syncope/branches/1_0_X/core/src/main/java/org/apache/syncope/core/workflow/NoOpUserWorkflowAdapter.java * /syncope/branches/1_0_X/core/src/main/java/org/apache/syncope/core/workflow/WorkflowResult.java * /syncope/branches/1_0_X/core/src/test/java/org/apache/syncope/core/rest/TaskTestITCase.java * /syncope/branches/1_0_X/core/src/test/resources/content.xml > Status is not updated when synchronizing existing users > --- > > Key: SYNCOPE-301 > URL: https://issues.apache.org/jira/browse/SYNCOPE-301 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.0.5, 1.1.0 >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 1.0.6, 1.1.0 > > > Even though the flag "Synchronize user status" is checked on the SyncTask, > the status (enabled / disabled) on the synchronizing external resources does > not make any suspend() / reactivate() to take place on Syncope, for existing > users. > For non-existing users, however, everything is working as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Syncope-trunk - Build # 37 - Fixed
The Apache Jenkins build system has built Syncope-trunk (build #37) Status: Fixed Check console output at https://builds.apache.org/job/Syncope-trunk/37/ to view the results.
[jira] [Commented] (SYNCOPE-301) Status is not updated when synchronizing existing users
[ https://issues.apache.org/jira/browse/SYNCOPE-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567441#comment-13567441 ] Francesco Chicchiriccò commented on SYNCOPE-301: Build fixed on trunk: https://builds.apache.org/job/Syncope-trunk/37/ > Status is not updated when synchronizing existing users > --- > > Key: SYNCOPE-301 > URL: https://issues.apache.org/jira/browse/SYNCOPE-301 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.0.5, 1.1.0 >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 1.0.6, 1.1.0 > > > Even though the flag "Synchronize user status" is checked on the SyncTask, > the status (enabled / disabled) on the synchronizing external resources does > not make any suspend() / reactivate() to take place on Syncope, for existing > users. > For non-existing users, however, everything is working as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
