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.
-- View this message in context: http://jackrabbit.510166.n4.nabble.com/Getting-multiple-nodes-in-one-call-with-davex-tp3565136p3566361.html Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
