Hi, I fell in this problem in past but I haven't found any killer solution.
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? Cheers Daniele -- 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.
