I was looking to encapsulate all the behavior of the account in an account object. So the object updates its self.
I'd say must people don't use that pattern anymore. That was my question. I have to go through all this coding and write all
these extra classes to be able to update info. right ? And I have to change the bussiness logic (AccountService) to suit this design.
It pays off to have a persistence layer, instead of mixing it up with you object model. I'm using JPA on top of Toplink and I'm quite happy with it, here is a tutorial, CRUD-like that you might want to take a look at: http://struts.apache.org/2.x/docs/struts-2-spring-2-jpa-ajax.html musachy -- "Hey you! Would you help me to carry the stone?" Pink Floyd
