The quoted comment is somewhat outdated. Documents can now overflow from one DTM ID to another, so the IDENT_DTM_NODE_BITS value is more a matter of efficiency than of actual document size limitation.
However: With current code, I'm surprised that you're actually managing to run out of DTM IDs unless you are using huge numbers of document() calls or doing extremely deep recursion of certain kinds of nested RTF construction. If you can come up with a reasonable-sized non-confidential testcase which demonstrates what you're doing to provoke the problem, it might be worth posting that to Bugzilla so we can consider whether there's something we need to do about it. Regarding "why does it have to be a compile-time setting?" -- I believe some Java compilers have fully inlined static-final compile-time constants. Hence, I would be concerned about making this reconfigurable at runtime; I'd want to see performance tests on a number of platforms before I'd be really comfortable with changing it to be a system property. And as mentioned above, I find myself wondering whether this is a matter of patching a symptom rather than fixing the actual disease. ______________________________________ Joe Kesselman -- Beware of Blueshift! "The world changed profoundly and unpredictably the day Tim Berners Lee got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
