The tables will get created automatically if you use hbm2ddl auto or update.

Adam

This should work without any problems. Can you see if AuditEventListener.initialize is getting called? (with a debugger)

Adam

I have the same issue. I'm using Spring and created a TestNG-integration test, in which everything works fine. When I try to integrate Envers in my application (using the same configuration), my Revision-Table gets generated, but no Audit-tables. I have set hbm2ddl.auto=update and the AuditEventListener.initialize-method gets called on startup. Any ideas where to look for an error?

I'm using Hibernate 3.5.1-FINAL.

Hmm if the initialize is called this "should" work - maybe make double sure that you have only one configuration file. Apart from that, you can try debugging the code that gets called in the initialization method - to see what happens there.

Adam

Thanks for the reply. After some trial & error and some more debugging it seems to be an issue with Spring and the way we use Hibernate in our project. We have a persistence module, where we define all database-relevant Spring beans (Session Factory, Transaction Manager...) as well as Envers. If I create an entity in this module and annotate it with @Audited, everything works as expected. However, for entities in other modules, no audit tables are created (however all other tables are created by hbm2ddl). My issue is probably due to the design of our application and not necessarily a problem with Envers, but to find the reason it would help to understand how (and where) Envers finds what entities should be audited.

Hello,

that's very weird ... the way Envers finds entities is simple: if you look at AuditEventListener, at the bottom there's an initialize method that accepts a Configuration. You can get a list of entities from that. Try to debug that method a little and I think you'll quickly see how it works

Adam

Hello,

I am having a similar issue, no audit tables are created and neither is the REVINFO table.

Added a breakpoint to AuditEventListener.initialize and that is called fine.  The Configuration passed to the AuditEventListener.initialize seems to have all the entities, so that also looks good.

The hbm2ddl is set as follows in the hibernate.cfg.xml file (Hibernate 3.6.5)

I am using Spring (2.5.6) and so have added the listeners to the spring file (snippet below).

But, although the app starts ok, no Enver Audit tables get generated, and if I try and alter the one entity that I have @Audited (com.gemini.database.domain.Configuration) I get the no table REVINFO found error:

Caused by: org.springframework.dao.InvalidDataAccessResourceUsageException: could not insert: [org.hibernate.envers.DefaultRevisionEntity]; nested exception is org.hibernate.exception.SQLGrammarException: could not insert: [org.hibernate.envers.DefaultRevisionEntity]

Caused by: java.sql.SQLException: Invalid object name 'REVINFO'.

I put debug logging on the envers pacakge (log4j.category.org.hibernate.envers=DEBUG) but all I get is:

DEBUG guration.metadata.AuditMetadataGenerator - Generating first-pass auditing mapping for entity com.hpdsoftware.gemini.database.domain.Configuration.

DEBUG guration.metadata.AuditMetadataGenerator - Generating second-pass auditing mapping for entity com.hpdsoftware.gemini.database.domain.Configuration.

Any ideas?  I'm a bit lost as to where to look next!

Cheers

Mat

I solved my issue - I think I may have imbibed too much last night.

Basically I needed to put the hbm2ddl.auto bit in my spring file, not the hibernate cfg file, i.e.

<property name="hibernateProperties">

    <props>

                <prop key="hibernate.show_sql">false</prop>

                <prop key="hibernate.hbm2ddl.auto">update</prop>                       

        </props>

</property>

As an aside, is it ok to have hibernate.hbm2ddl.auto as update in a production system?

Hi!

You can use variables for these properties and set them from outside. I'm using spring properties holders to achieve this.

Regards. Hernán.

Great to hear it works

As for the question if update is safe for production - personally I usually have it set to validate, and generate the SQL update scripts using the staging/test database. But if you have a good staging environment, so that you can test the update before pushing it to production, I don't see a reason not to use it

Adam