> employeeDAO.updateEmployee( employee ); > > From what I recall the real OO way would be... > > employee.update(); > > and employee takes care of updating itself. >
I made a BaseBO using OJB, which has the create, update, softDelete, hardDelete, findById, findByCriteria methods. It also has an id and deleted fields. Any other BOs extend it, and inherit the behaviours. The only tie to OJB in any class other than BaseBO is the Criteria and QueryByCriteria classes which are used for any queries other than findById, which i cant see a way round. The only downside is writing the mappings for each class (though this can be simplified using XDoclet). It works wonderfully, and saved lots of coding. Daniel. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
