You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/09/18 15:09:52 UTC
[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