Re: using hibernate pojo as model instead of dto

get fields from different entities then maybe you should > consider dto. > -- > View this message in context: > http://www.nabble.com/using-hibernate-pojo-as-model-instead-of-dto-tp25071549p25079082.html > Sent fr

Re: using hibernate pojo as model instead of dto

-- View this message in context: http://www.nabble.com/using-hibernate-pojo-as-model-instead-of-dto-tp25071549p25079082.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: user

Re: using hibernate pojo as model instead of dto

Am Donnerstag, den 20.08.2009, 18:59 -0700 schrieb fachhoch: > Is this is a good design or using DTO is a good desing ? it depends.. (IMHO there are only some situations where you can see some benefit in DTO) .. but you have to use LoadableDetachableModels or custom Model implementations to avoid

Re: using hibernate pojo as model instead of dto

Is this is a good design or using DTO is a good desing ? Mathias Nilsson wrote: > > You can use entities as models. Just use LoadableDetachableModels to avoid > LazyLoadingExceptions > -- View this message in context: http://www.nabble.com/using-hibernate-pojo-as-model-in

Re: using hibernate pojo as model instead of dto

You can use entities as models. Just use LoadableDetachableModels to avoid LazyLoadingExceptions -- View this message in context: http://www.nabble.com/using-hibernate-pojo-as-model-instead-of-dto-tp25071549p25072411.html Sent from the Wicket - User mailing list archive at Nabble.com

using hibernate pojo as model instead of dto

I am wondering If it is write to use hibernate pojo entities as model objects for wicket components , or should I create a DTO and use them as model objects , Is there any disadvantages of using entities POJO's as model ?