2015-04-21 8:51 GMT+02:00 gantners <[email protected]>: > > > Am Dienstag, 21. April 2015 07:23:12 UTC+2 schrieb Daniele Antonini: >> >> Hi, >> I fell in this problem in past but I haven't found any killer solution. > > Good to hear that, i googled a lot and since there is no real solution to > this Problem, i just felt like i´m the only one who is not willing to > introduce that much complexity with a whole different query Syntax like the > criteria api. i still want to write plain SQL queries no hql or jpql. > >> >> >> Sure you can use model mapper / dozer to speedup the writing of >> conversion code. Sometimes I found useful do not use any of these framework >> and write the conversion code by myself.. Yeah it a little boring activity >> but in this way you cut off the complexity of the conversion layer. >> >> For my point of view the real problem is that hibernate session is out >> due to the client constraints. In this scenario use hibernate (session per >> request) could be inappropriate. You can have advantages if your data >> structures are entities these fit your needs. >> But When your entities aren't enough, and you need of very different data >> structures, >> well, you could have more success with pure sql or jooq (if you use a >> rdbms, I haven't any experiences with nosql or object database). >> >> An overview: >> - Hibernate is a fat layer >> - Model mapper is a thin layer (slippery enough) >> >> Do you really need to introduce this complexity in you project? > > > modelmapper makes only sense for me if i would have a clean database > Modell where i can assume all those naming convetions to really generically > do the mapping. at the Moment you Need to specifiy a lot of specialised > mappers du to bad named columns/pojos it takes too much time. so you would > rather go and clean the database model first, which can be a lot of work in > the first place but that is where the economists deny :) > > What i´m really looking for, is a small footprint Technology to add the > lazy loading mechanism (because of entities in entities) no matter how the > Client is connected(in my case rmi). a somewhat intelligent pojo, which > knows when to load the rest. I do not like to tie me to session Management, > as i prefer staying stateless. For the mapping itself in my Point of view, > jdbctemplate and it´s rowmapping functionality should be enough for the > mapping. > so at the Moment it Looks like i´m about to implement this myself... >
Well, jOOQ has RecordMappers, which help you translate flat Records to your own data structure. You can also register / override the DefaultRecordMapper as described here: http://www.jooq.org/doc/latest/manual/sql-execution/fetching/pojos-with-recordmapper-provider/ I don't think you'll get anything out of jdbctemplate that you couldn't get out of jOOQ as well... -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
