Best OO design

Hi,

I am currently developing a online system that has front end and back end server. The front end server will send a request to back end thru web service. THe request header contains some critical Transfer objects like Bank Account, Customer Account....etc. ALl of them extends the super class called "Auditable Bean" which has the setter and getter of "last update staff" and "last updated timestamp". SInce my request object has the value of "last update staff", what I need to do is to set it to all the transfer object once the back end receives the request, like CustomerAccount.setLastUpdateStaff(request.getLastUpdateStaff), and same way in BankAccount.setLastUpdateStaff(request.getLastUpdateStaff).

I want to ask is there better way to handle this so that I won't have to set it one by one in the back end server ? I want to make the best OO decision so that I won't have to rework again in the future, please advice..thanks

Transistor

[976 byte] By [popohomaa] at [2007-10-3 10:57:25]
# 1
I have absolutely no idea what you're actually asking. can you re-phrase, in a more linear way, please?if you're asking "is there a design pattern that will solve this?", no, there isn't. patterns != magic beans :-)
georgemca at 2007-7-15 6:23:30 > top of Java-index,Other Topics,Patterns & OO Design...