Specifying RevisionListener.class on @RevisionEntity

[appletree]

We are following the guidelines specified here for adding a listener so that we can update our RevisionEntity.  The problem is that we have our code segmented into different maven modules with our model being in 1 module and our persistence code in another.  This helps us in other ways, but the problem is our RevisionListener.class needs to use code that is in other modules which depend on our model module.  Our workaround is ugly...

I guess my question is, is there another way to specify a RevisionListener for a RevisionEntity?

[adamw]

Not yet, but patches, or rather - pull requests - are very welcome

Shouldn't be hard to add the possibility to specify the rev listener using a configuration property.

Adam

[slominskir]

Any news on this? 

I'd like to add a listener to add a username and client IP address to the revision entity.  The client IP address information comes from the presentation layer, but registering a presentation layer listener in the business / persistence layer tightly couples them together.

Using the AuditReader.getCurrentRevision alternative is no good because then you're mixing the auditing cross-cutting concern with business logic.

[adamw]

Not really, but as I said - ideas on how to solve that problem & patches are always welcome

Adam

[slominskir]

Maybe we can use CDI to solve this issue?

[adamw]

Well you could lookup the BeanManager in your revision listener and invoke anything from there - that would be essentialy a static lookup.

Or did you mean something else?

Adam

[slominskir]

Well any dependency injection approach is convenient.  I suppose adding a dependency in Envers on CDI is no good though so I guess a configuration file or lookup via the BeanManager or any service locator (JNDI?) would be good choices.

[adamw]

Yeah, well first you need to get the BeanManager from JNDI

Adam

[adamw]

See: https://hibernate.onjira.com/browse/HHH-6696

This will be included in the next release of Hibernate 4.

Adam