On 01.06.2011, at 19:06, mmjose26 <[email protected]> wrote: > I had the same problem, because davex do a request for each > Session.getNode(path). but if you have some common property in nodes or in > paths, you could try with a SQL2Query and query only for properties that you > need at first time (avoid binary content for best performance), and in > second time get all detail of only one node of interest.
that is quite a list of limitations but its of course a solution for some use cases. but that leaves enough use cases out of the loop, so we should definately add a getNodes to JCR 2.1. especially since the burden on implementors that do not want to optimize is very low. regards Lukas
