I'm working on a JPA (Hibernate implementation of), Spring and Stripes web app. I have a number of JPA entities that have the following fields in common for both audit and query purposes:
createdBy - the user ID of the person who created the entity. createdOn - the date the entity was created updatedBy - the user ID of the person who last updated the entity updatedOn - the date the entity was last updated
I've got my app working so that createdOn and updatedOn are set automatically when the entity is persisted but I'm not sure how I can get the createdBy and updatedBy fields populated without having to pass through the currently logged in user's ID all the way from the controller class to the DAOs.
Does anyone have any suggestions on how I might do this without passing userIDs all over the place? Note that the current user ID is stored in the HttpSession object at the moment, so my backend needs to somehow access this data...
Thanks!
You can have a look at one of these approaches to pass the user ID as context in the business layer:
(The posts may still be relevant even if you're not using EJB. The second post make sense however only if you use Spring with JTA)
I personally discourage these approach, as I perceive two problem with it:
Passing userID "all over the place" may seem like a big job, but I think it's cleaner.
To set the date and user ID automatically when entity is created or update, you can use an EntityListener or lifecycle callbacks (maybe you're already doing that). Hope it helps...
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With