[jira] [Created] (SYNCOPE-414) Cannot successfully deploy on Weblogic 12c (12.1.1)
Francesco Chicchiriccò created SYNCOPE-414: -- Summary: Cannot successfully deploy on Weblogic 12c (12.1.1) Key: SYNCOPE-414 URL: https://issues.apache.org/jira/browse/SYNCOPE-414 Project: Syncope Issue Type: Bug Components: console, core Affects Versions: 1.2.0 Environment: Weblogic 12c (12.1.1) Reporter: Francesco Chicchiriccò Fix For: 1.2.0 Due to LOG4J2-344 and / or LOG4J2-359, deploy core or console on Weblogic is not working -- 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: EntityValidationInterceptor / log level of bean validation errors
Il 10/09/2013 15:18, Francesco Chicchiriccò ha scritto: On 10/09/2013 13:27, Guido Wimmel wrote: Hi, currently, EntityValidationInterceptor logs bean validation errors with log level ERROR. I think bean validation errors can be part of normal system behaviour (e.g. a user registers itself or is registered by an admin and accidentally or unknowingly enters invalid data and then gets an error message on the UI). We configured our system to send notifications to the operations team on ERROR log events and would have to filter this one out. I'd suggest turning the log level to WARN or maybe even INFO, but it can also be that I have overlooked some use cases where ERROR would indeed be appropriate. Hum, not sure I agree: are you suggesting that a bean validation error is not an actual operational error, hence it shouldn't be logged as ERROR? I can hardly figure them out as WARN... Someone else's opinion? Maybe, WARN is better. I have to agree with Guido. @Guido can you open a new issue and attach the patch? Best regards, F.
Re: EntityValidationInterceptor / log level of bean validation errors
On 18/09/2013 10:31, Fabio Martelli wrote: Il 10/09/2013 15:18, Francesco Chicchiriccò ha scritto: On 10/09/2013 13:27, Guido Wimmel wrote: Hi, currently, EntityValidationInterceptor logs bean validation errors with log level ERROR. I think bean validation errors can be part of normal system behaviour (e.g. a user registers itself or is registered by an admin and accidentally or unknowingly enters invalid data and then gets an error message on the UI). We configured our system to send notifications to the operations team on ERROR log events and would have to filter this one out. I'd suggest turning the log level to WARN or maybe even INFO, but it can also be that I have overlooked some use cases where ERROR would indeed be appropriate. Hum, not sure I agree: are you suggesting that a bean validation error is not an actual operational error, hence it shouldn't be logged as ERROR? I can hardly figure them out as WARN... Someone else's opinion? Maybe, WARN is better. I have to agree with Guido. Well, time brought some more wisdom to me as well: I agree with the proposed change. Regards. @Guido can you open a new issue and attach the patch? -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
[jira] [Commented] (SYNCOPE-414) Cannot successfully deploy on Weblogic 12c (12.1.1)
[ https://issues.apache.org/jira/browse/SYNCOPE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770583#comment-13770583 ] Hudson commented on SYNCOPE-414: SUCCESS: Integrated in Syncope-trunk #444 (See [https://builds.apache.org/job/Syncope-trunk/444/]) [SYNCOPE-414] Minor adjustments (ilgrosso: rev 1524335) * /syncope/trunk/core/src/main/webapp/WEB-INF/web.xml * /syncope/trunk/core/src/main/webapp/WEB-INF/weblogic.xml > Cannot successfully deploy on Weblogic 12c (12.1.1) > --- > > Key: SYNCOPE-414 > URL: https://issues.apache.org/jira/browse/SYNCOPE-414 > Project: Syncope > Issue Type: Bug > Components: console, core >Affects Versions: 1.2.0 > Environment: Weblogic 12c (12.1.1) >Reporter: Francesco Chicchiriccò > Fix For: 1.2.0 > > > Due to LOG4J2-344 and / or LOG4J2-359, deploy core or console on Weblogic is > not working -- 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-246) Remove collection setters in transfer objects for JAXB marshalling
[ https://issues.apache.org/jira/browse/SYNCOPE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770627#comment-13770627 ] Hudson commented on SYNCOPE-246: SUCCESS: Integrated in Syncope-trunk #445 (See [https://builds.apache.org/job/Syncope-trunk/445/]) [SYNCOPE-246] Residual invocation that cannot be checked at compile time due to non-generic nature of the collection (List) (ilgrosso: rev 1524341) * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/ConnectorModalPage.java > Remove collection setters in transfer objects for JAXB marshalling > -- > > Key: SYNCOPE-246 > URL: https://issues.apache.org/jira/browse/SYNCOPE-246 > Project: Syncope > Issue Type: Sub-task > Components: core >Affects Versions: 1.1.0 > Environment: CXF branch >Reporter: Andrei Shakirin >Assignee: Francesco Chicchiriccò > Fix For: 1.2.0 > > > XML payload will be marshaled/unmarshaled using JAXB by migration to CXF Rest > frontend. > JAXB works with collections in a little bit different way as Spring Rest > marshaling. > JAXB uses only getter for the list (assumes that list is initialized due > object creation) and adds elements into the list obtained by getter by > unmarshaling. It doesn't need setter at all. > The problem is that actual implementation of transfer objects doesn't work > with JAXB. > If TO provide setter for collection, JAXB gets the list, adds the elements > and additionally calls setter for this list. As far as setter logic cleans > the TO collection, the result collection is always empty. > Solution is remove setters for collections in TOs by migration on CXF Rest. > I find it also better from security and encapsulation aspects. > Regards, > Andrei. -- 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-412) Audit tables are reset after restart
[ https://issues.apache.org/jira/browse/SYNCOPE-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-412. Resolution: Fixed http://svn.apache.org/r1524383 > Audit tables are reset after restart > > > Key: SYNCOPE-412 > URL: https://issues.apache.org/jira/browse/SYNCOPE-412 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.3 >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Labels: audit > Fix For: 1.1.4 > > > Due to the way how logback audit SQL init scripts are architected, audit > tables are dropped and re-created at every Syncope restart. -- 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-150) Rich client library
[ https://issues.apache.org/jira/browse/SYNCOPE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-150: -- Assignee: Francesco Chicchiriccò > Rich client library > --- > > Key: SYNCOPE-150 > URL: https://issues.apache.org/jira/browse/SYNCOPE-150 > Project: Syncope > Issue Type: New Feature >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 1.2.0 > > > Implement a client library that can be encapsulated in a single JAR, > providing client access to all features. -- 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-405) Replace logback with log4j 2
[ https://issues.apache.org/jira/browse/SYNCOPE-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770747#comment-13770747 ] Hudson commented on SYNCOPE-405: SUCCESS: Integrated in Syncope-1_1_X #106 (See [https://builds.apache.org/job/Syncope-1_1_X/106/]) [SYNCOPE-412] Backporting to 1_1_X part of audit SQL management from SYNCOPE-405 (ilgrosso: rev 1524383) * /syncope/branches/1_1_X/core/pom.xml * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/audit/JNDIFallbackConnectionSource.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/dao/impl/AbstractContentDealer.java * /syncope/branches/1_1_X/core/src/main/resources/audit.xml * /syncope/branches/1_1_X/core/src/main/resources/logback/h2.sql * /syncope/branches/1_1_X/core/src/main/resources/logback/hsqldb.sql * /syncope/branches/1_1_X/core/src/main/resources/logback/mysql.sql * /syncope/branches/1_1_X/core/src/main/resources/logback/oracle.sql * /syncope/branches/1_1_X/core/src/main/resources/logback/postgresql.sql * /syncope/branches/1_1_X/core/src/main/resources/logback/sqlserver.sql * /syncope/branches/1_1_X/core/src/main/resources/syncopeContext.xml > Replace logback with log4j 2 > > > Key: SYNCOPE-405 > URL: https://issues.apache.org/jira/browse/SYNCOPE-405 > Project: Syncope > Issue Type: Improvement >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 1.2.0 > > > As discussed in dev ML [1] > [1] > http://syncope-dev.1063484.n5.nabble.com/DISCUSS-Replace-logback-with-log4j-2-td5714012.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-412) Audit tables are reset after restart
[ https://issues.apache.org/jira/browse/SYNCOPE-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770748#comment-13770748 ] Hudson commented on SYNCOPE-412: SUCCESS: Integrated in Syncope-1_1_X #106 (See [https://builds.apache.org/job/Syncope-1_1_X/106/]) [SYNCOPE-412] Backporting to 1_1_X part of audit SQL management from SYNCOPE-405 (ilgrosso: rev 1524383) * /syncope/branches/1_1_X/core/pom.xml * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/audit/JNDIFallbackConnectionSource.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/dao/impl/AbstractContentDealer.java * /syncope/branches/1_1_X/core/src/main/resources/audit.xml * /syncope/branches/1_1_X/core/src/main/resources/logback/h2.sql * /syncope/branches/1_1_X/core/src/main/resources/logback/hsqldb.sql * /syncope/branches/1_1_X/core/src/main/resources/logback/mysql.sql * /syncope/branches/1_1_X/core/src/main/resources/logback/oracle.sql * /syncope/branches/1_1_X/core/src/main/resources/logback/postgresql.sql * /syncope/branches/1_1_X/core/src/main/resources/logback/sqlserver.sql * /syncope/branches/1_1_X/core/src/main/resources/syncopeContext.xml > Audit tables are reset after restart > > > Key: SYNCOPE-412 > URL: https://issues.apache.org/jira/browse/SYNCOPE-412 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.3 >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Labels: audit > Fix For: 1.1.4 > > > Due to the way how logback audit SQL init scripts are architected, audit > tables are dropped and re-created at every Syncope restart. -- 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-407) Add claim for user requests and trace user request history into SyncopeUser bean
[ https://issues.apache.org/jira/browse/SYNCOPE-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-407. Resolution: Fixed > Add claim for user requests and trace user request history into SyncopeUser > bean > > > Key: SYNCOPE-407 > URL: https://issues.apache.org/jira/browse/SYNCOPE-407 > Project: Syncope > Issue Type: Improvement > Components: client, console, core >Affects Versions: 1.1.3, 1.2.0 >Reporter: fabio martelli >Assignee: fabio martelli > Fix For: 1.2.0 > > > Add claim for user requests and trace user request history into SyncopeUser > bean -- 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-407) Add claim for user requests and trace user request history into SyncopeUser bean
[ https://issues.apache.org/jira/browse/SYNCOPE-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770967#comment-13770967 ] Hudson commented on SYNCOPE-407: SUCCESS: Integrated in Syncope-trunk #447 (See [https://builds.apache.org/job/Syncope-trunk/447/]) SYNCOPE-407 fixed (fmartelli: rev 1524459) * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/UserRequestService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/UserRequestTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/AuditElements.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/SyncopeClientExceptionType.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/Todo.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/ConnectorRestClient.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/UserRequestRestClient.java * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/Todo.html * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/Todo.properties * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/Todo_it.properties * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/Todo_pt_BR.properties * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/beans/UserRequest.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/dao/UserRequestDAO.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/dao/impl/UserRequestDAOImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/UnauthorizedException.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/UserRequestController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/UserRequestServiceImpl.java * /syncope/trunk/core/src/main/resources/content.xml * /syncope/trunk/core/src/main/resources/quartz/tables_sqlServer.sql * /syncope/trunk/core/src/test/java/org/apache/syncope/core/persistence/dao/EntitlementTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserRequestTestITCase.java * /syncope/trunk/core/src/test/resources/content.xml > Add claim for user requests and trace user request history into SyncopeUser > bean > > > Key: SYNCOPE-407 > URL: https://issues.apache.org/jira/browse/SYNCOPE-407 > Project: Syncope > Issue Type: Improvement > Components: client, console, core >Affects Versions: 1.1.3, 1.2.0 >Reporter: fabio martelli >Assignee: fabio martelli > Fix For: 1.2.0 > > > Add claim for user requests and trace user request history into SyncopeUser > bean -- 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
