I like @Auditable because it's easy to switch on auditing of specific entities or entity hierarchies. But the property would allow for auditability globally to be turned on or off. Personally I would favour also adding a property like :
<property name='openjpa.AuditManagerImpl" value="com.mypackage.MyAuditManager"/> Different countries and industries have different audit requirements so we can implement/extend to our specific requirements. 2c more :) Chris -----Original Message----- From: Pinaki Poddar [mailto:ppod...@apache.org] Sent: Tuesday, 8 June 2010 10:20 PM To: users@openjpa.apache.org Subject: Re: JPA for portable database management (and wishes for JPA 3.0) > some technical annotation like @NativeTrigger or should we have higher > level annotation like @Audit ? I prefer @Audit to @NativeTrigger. In fact I see two specifications a) one on the persistent domain entity as an annotation @Entity @Auditable public class Customer {....} b) one on the run-time as a plug-in property <property name="openjpa.AuditManager" value="trigger(query=false, table=true)"/> or <property name='openjpa.AuditManager" value="none"/> ----- Pinaki -- View this message in context: http://openjpa.208410.n2.nabble.com/JPA-for-portable-database-management-tp5 134215p5153394.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
