-
-
Notifications
You must be signed in to change notification settings - Fork 358
-
-
Notifications
You must be signed in to change notification settings - Fork 358
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deactivating @JaversSpringDataAuditable by configuration #435
Comments
You mean in spring boot starter? |
Yes in the spring boot starter |
Could you describe your use case? I wonder if this feature would be useful for other javers users |
Hi. I got some MongoRepositories to which i added the Annotation "JaversSpringDataAuditable". The Annotation does what it should do, but for a reason, i dont know yet, our software is obviously slower with these Annotations. So i would like to deactivate the creating the snapshots of the entities until i find the problem. At the moment i comment out these annotations. A better solution wouldbe that i can add a property in my spring boot config with the name "auditEnabled" and then add some logic which activates/deactivates the creating of snapshots depending on the value of this property. Or in other words: it would be good to deactivate/activate the Annotations by only changing one line. I hope the intention is clear now. |
Right, think about a PR. It looks like a small change in javers-spring-boot-starters configuration |
…ication #435 auditable aspects deactivation
fixed in release 2.6.0 |
Hi.I would like to activate/deactivate the functionality of the Annotation @JaversSpringDataAuditable by a configuration property.
Can the contructor of "JaversSpringDataAuditableRepositoryAspect" be changed so that i can commit an own implementation of "OnSaveAuditChangeHandler". So the method "handle" can only invoke the commit only if the configuration property is active.
Or is there a better wy for my intention ?
The text was updated successfully, but these errors were encountered: