DO and Entitybean mapping(how to)

Question

I have used a tool to generate entity beans and its related artifacts such as corresponding DAO and DAO implementation as described here
http://www.hibernate.org/328.html
I have also modelled my Domain Objects Nicely. Now am stuck in anemic coding.
http://www.martinfowler.com/bliki/AnemicDomainModel.html
to use proper MVC, i have to populate the beans of the web-client manually or sometimes using BeanUtils. However, sometimes the View Bean has no relation to
the EntityBean, and I end up copying the bean manually
setMyUsername(entity.getusrname());This design have several bad flaws
1. Just because i dont want the jsp to be tied to the entity, i do all this maual copying into a completely redundant bean that have nothing like state or behaviour
2. I have to copy the data back into the entity on form submission. another redundant code
3. the enity bean is directly dependent on database structure which make the database bleed into the view
4. I then have to map the model back to the bean or vice versa to do business logic like permissions and validation. another round of copying
I have looked at DTOs but dont know how to do it dynamically
Can someone propose a design that will solve my problem

Answer 1

nothing will read your mind, but Spring's DataBinding framework does very well.
%