thanks. great news.
the depth of the object graph is indeed what still needs to be discussed. i think i have posted already some ideas before on this dev forum.
probably the most easy solution is to just resolve the minimal graph (only using hibernate's lazy loading) and then using inheritence for expanding this graph as needed. if a user wants a more deeply resolved objectgraph, he/she can just subclass the original command and add navigation to activate lazy initialization.
what do you think ?
probably the most easy solution is to just resolve the minimal graph
The question is: What is the minimal graph? If I only return a ProcessInstance for example, I even do not have the root token! So I think, thats not a real valuable graph for the client.
Subclussing is indeed a good solution, but to have a subclass for each and every use case is not so nice. So I think we need a tradeoff between performance and "usability".
What do you think about the current pre-fetching (you can look at it in one class: AbstractGetObjectBaseCommand), too deep?