#1672 new
notalifeform (at gmail)

Hibenate envers audit configuration not supported

Reported by notalifeform (at gmail) | May 23rd, 2013 @ 07:24 PM | in 1.4.x

(as per thread https://groups.google.com/forum/?fromgroups=#!topic/play-framework/...)

Hello Richard,

No, I did not. However, as I said, our "basic" envers configuration was working. We were using the same configuration as the one mentioned in the link you have provided.

My problem was to make a specific Enevers configuraiton work, regarding the new Audit Strategy they have implemented. The configuration parameters do not start with "hibernate...." but "org.hibernate...". In the Play framework, I have clearly identified a piece of code where the framework injects configuration in Hibernate and this is done like this:

cfg.addProperties((Properties) Utils.Maps.filterMap(Play.configuration, "^hibernate\..*"));

This line clearly ignores all configuration regarding the Audit Strategy configuration (you can find this configuration here) whose all parameters begin with "org.hibernate".

By the way, thank you for your answer.

Regards,
Anthony

Le jeudi 23 mai 2013 13:07:56 UTC+2, Richard a écrit :
- hide quoted text - Hi, have you seen this?
http://java-semantics.blogspot.nl/

Comments and changes to this ticket

  • Alex

    Alex May 24th, 2013 @ 12:36 AM

    • Tag set to audit, envers, hibernate

    I don't know if you use a module to use Envers. But in my case we developed a specific module do handle all audit staff, so we jusst all configurations we want by overriding the function onConfigurationRead in our module

    public void onConfigurationRead() {
            Play.configuration.setProperty("hibernate.ejb.event.post-insert", "play.modules.audit.xxxxxClass");
    
            Play.configuration.setProperty("org.hibernate.envers.audit_strategy", "org.hibernate.envers.strategy.ValidityAuditStrategy");
    }
    

    This way you can specify all properties you need

  • notalifeform (at gmail)

    notalifeform (at gmail) April 27th, 2014 @ 12:06 PM

    • Milestone changed from 1.3 to 1.4.x

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

Pages