Hi Carl, I posted a message to this thread but it somehow got lost. We have the same problem in a current project but we are not using a ORM but JSON for storage. We are using a builder to deserialize the JSON and create a immutable object out of it. I have an experiment up on GitHub. Maybe it is helpful to you: https://github.com/shimberger/jackson-builder-module
In JSON it is easy since the structure is always a tree and there are only parent/child relationships. This means we just have to construct the children before the parent. I somehow find that having complex object graphs make it difficult to modularize your application anyway. I tend to model references explizitly using IDs. Maybe I am just too much of a database person. This also get's around the whole lazy-loading issue. But I guess you loose a rich domain model It is a very interesting issue discussion. Your thought makes sense to me. Bi-directional relationships seem to be an issue. Merry Christmas, Sebastian -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/8WSQa4T-DVQJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
