PaloT wrote: > > For now I'm generating it instead of auditable. This mean that all > entities which are auditable are populated with FullAuditLog. What's > your opinion about this, is better to customize it per Entity or per > model in properties file? If per Entity we should use hints. > Another question is if fullAudit is extension to audit feature or is > totally separate? >
I think there is no need for configuration per entity. That can be done with aop customization (and hint) if someone need it. I think it should be a generator property to define if brief of full audit should be used. generate.fullAudit=false PaloT wrote: > >> What is the advantage over AuditListener? Or is it needed for >> FullAuditLog? > Only reason is, easy code generation. I found some "abscure" > constructs for Entity level annotations. With listener it will be > difficult to call protected setUpdate.... methods. > protected methods is a good advantage. We should avoid generate duplicated code so I would like that the lastUpdatedBy() method is moved to an utility. I suggest that we move it to a static method in ServiceContextStore and name it currentUser() /Patrik -- View this message in context: http://www.nabble.com/New-extensions-tp24936915s17564p25010889.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Fornax-developer mailing list Fornax-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fornax-developer
