Some Tradista objects use audit fields (ex: creation or last update time), the code can be improved to control how these fields are set.
We should also ensure that they are displayed with a time zone that makes sense to the users.
A solution to control creations/updates on these fields is to use the Builder design pattern. That would also be a way to unify how these objects are managed.
Also, the Instant type should be used to represent these fields. Indeed, what is required to be stored is the exact time, independently of any time zone.
On another hand, the time zone makes sense to the end users, so these fields should be converted to ZonedDateTime objects when displayed in Tradista GUI.
The time zone used in the GUI should be the one of the user's PO.
Please refer to what has been done for the Message objects. Check Message objects and DAO, check also the UserManagement class and message.xhtml
Some Tradista objects use audit fields (ex: creation or last update time), the code can be improved to control how these fields are set.
We should also ensure that they are displayed with a time zone that makes sense to the users.
A solution to control creations/updates on these fields is to use the Builder design pattern. That would also be a way to unify how these objects are managed.
Also, the Instant type should be used to represent these fields. Indeed, what is required to be stored is the exact time, independently of any time zone.
On another hand, the time zone makes sense to the end users, so these fields should be converted to ZonedDateTime objects when displayed in Tradista GUI.
The time zone used in the GUI should be the one of the user's PO.
Please refer to what has been done for the Message objects. Check Message objects and DAO, check also the UserManagement class and message.xhtml