You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 23, 2021. It is now read-only.
we use Envers in OASP4J to do auditing of the database as described in the Devonfw Guide paragraph 3.12.2 “Auditing with Hibernate Envers”., the issue relates to some instances that the database is at application startup in read-only mode or the REVINFO (which Envers uses) is not present. This leads to an application crash.
So, for this problem , we need to have a property in applications.properties which allows us to disable the envers mechanism so that the application will not crash.
The property which is used to enable/disable envers is available in hibernate-envers-5.0.1-Final.jar but not in the existing one being used.
So , introduction of newer version should be done.
The text was updated successfully, but these errors were encountered:
@PriyankaBelorkar thanks for your feedback and sorry for the extra ordinary late response.
We will surely update envers dependency to an even more recent version than you proposed. I hope and plan to have that in 3.0.0 where we also do major updates to spring and spring-boot anyways.
Link to the place: https://github.com/oasp/oasp4j/blob/develop/bom/pom.xml#L119
we use Envers in OASP4J to do auditing of the database as described in the Devonfw Guide paragraph 3.12.2 “Auditing with Hibernate Envers”., the issue relates to some instances that the database is at application startup in read-only mode or the REVINFO (which Envers uses) is not present. This leads to an application crash.
So, for this problem , we need to have a property in applications.properties which allows us to disable the envers mechanism so that the application will not crash.
The property which is used to enable/disable envers is available in hibernate-envers-5.0.1-Final.jar but not in the existing one being used.
So , introduction of newer version should be done.
The text was updated successfully, but these errors were encountered: