Entity to DTO conversion with JPA?

Your DTOs are probably too fine-grained. I.e. Don't plan to have a DTO per JPA entity.

If you have to use DTOs then make them more coarse grained and construct them manually.

Your DTOs are probably too fine-grained. I.e. Don't plan to have a DTO per JPA entity.

If you have to use DTOs then make them more coarse grained and construct them manually. Recently we have had the whole "to DTO or not to DTO, that is the question" discussion AGAIN. The requirement for them (especially in the context of a JPA app) is often no longer there, but one of the arguments FOR DTOs tends to be that the view has coarser data requirements.

– Hugo Feb 15 '10 at 15:57 1 It really depends on your application and how you are architecting it. You talk about it being a Web application but in the same breath you are concerned about things being sent over the wire. What wire?

The wire between the appserver and the database or the logical wire between the view and the model/controller layer, or the wire between a browser AJAX call and the server? – Craig Day Feb 16 '10 at 13:45 1 Mainly, the wire between the browser and server, but I'd also like to reduce the DB java server data getting trasmited as well... I guess lazy loading and using one dto per view works, since when converting the model to , I won't accidentaly lazy-load unnecesary data, and I only send what the view needs. It's more work (lots more classes) but I see no choice.

Thanks. – Hugo Feb 17 '10 at 0:40.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.