We are looking at using Envers to audit several of our entities and I have been looking at the documentation and have two questions that I am hoping someone can answer:
1. It looks like the fluent interface for configuring entity auditing is an exclusion model where all of the mapped properties of the entity are audited by default unless a property is explicitly excluded. We plan to do run time configuration of the audited properties based on information provided by the user and would prefer to have an inclusion model were we specify in fluent the fields to include. So far it looks like this is not supported in the fluent interface. Am I correct? 2. We have a requirement to always include certain attributes in the audit that are part of the entity being tracked, but *we do not want changes to these specific attributes to trigger an audit record*. In a sense they just come along for the ride and would load into the entity when we query with the AuditReader. I see that the RevisionEntity can store additional information, but that does not seem to be the correct solution for us since I don't believe that the RevisionEntity information will load back into the entities property during the query. Is there a straight-forward way to support this requirement with Envers? Thanks for any guidance that you can provide. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/OVi89ImRB4MJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
