Hi Peeter,
Peeter Piegaze wrote:
On 4/19/06, Marcel Reutegger <[EMAIL PROTECTED]> wrote:
Florent Guillaume wrote:
I have a node that has lots of unordered children nodes. Some of these
nodes are "real children" in the document management sense, the others
(in small number) are just nodes that hold complex datatypes but are
really part of the main document.
I'd like to access both categories of nodes in an efficient manner:
- get only the nodes for my complex datatypes,
- get the list of "real children" nodes.
when you say 'get a list of child nodes' isn't it easier just using the
api instead of a query? Node.getNodes() and then have a custom
NodeIterator that filters out unnecessary nodes?
Or you could simply push one or both categories of nodes down one
level by defining an intervening node. Then you would just get *that*
node and get its children.
Yes, that was the other solution I'd envisioned. I'll fallback to this if
performance is not adequate using other node organizations.
Thanks for your comments,
Florent
--
Florent Guillaume, Nuxeo (Paris, France) Director of R&D
+33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED]
