http://www.homik.de/think/index.php/2008/04/08/automatic-timestamping-of-persisted-data/ Tue, 29 Jun 2010 23:11:01 +0200 http://wordpress.org/?v=2.9 hourly 1 http://www.homik.de/think/index.php/2008/04/08/automatic-timestamping-of-persisted-data/comment-page-1/#comment-3167 Martin Homik Mon, 19 May 2008 07:21:53 +0000 http://www.homik.de/think/index.php/2008/04/08/automatic-timestamping-of-persisted-data/#comment-3167 No, finally I solved it (maybe less elegant) in the Logic Layer by overwriting the save method. There I set the 'modified' field to the current date. Depending on whteher the POJO is a new entity I also set the created date timestamp. In the last step I call the save method of the super class. No, finally I solved it (maybe less elegant) in the Logic Layer by overwriting the save method. There I set the ‘modified’ field to the current date. Depending on whteher the POJO is a new entity I also set the created date timestamp. In the last step I call the save method of the super class.

]]> http://www.homik.de/think/index.php/2008/04/08/automatic-timestamping-of-persisted-data/comment-page-1/#comment-3165 anonymous Mon, 19 May 2008 03:43:58 +0000 http://www.homik.de/think/index.php/2008/04/08/automatic-timestamping-of-persisted-data/#comment-3165 Did you end up implementing the spring AOP interceptor? Did you end up implementing the spring AOP interceptor?

]]>