If it is possible to put the ManagedBean in RequestScope you could call the createAuditEntry method in the bean`s constructor. Then it is only called once per request.
If it is possible to put the ManagedBean in RequestScope you could call the createAuditEntry method in the bean`s constructor. Then it is only called once per request. Regards.
Unfortunately the bean is already RequestScoped and I tried auditing on the bean constructor. However there is a Class Instantiation exception due to updated DataTable Column on my post :( – camiloqp Mar 4 at 20:00 Well I found the problem.. Since the Backing Bean is request scoped, it will instantiate a new bean each time a different page of the DataTable is selected and thus will generate a new Audit Entry... I will have to make the Backing Bean work as view scoped.. – camiloqp Mar 4 at 20:20 It would be interesting to know if you get rid of the exception by changing the scope. – Matt Handy Mar 4 at 20:28.
Solved my problem. The backing bean is now ViewScoped and I just created a Boolean variable which ensures the Auditing is only done once per Bean ViewScope cycle. Public List getAllAuditEntries() { if (!isViewed) { isViewed = true; auditFacade.
CreateAuditEntry( __creates Audit Entry here__); } return allAuditEntries; }.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.