OK thanks very much for your answers. I thought that DTM was *just* an
optimization.
I had not understood that it was rather an in-depth implementation choice.
By the way what's the meaning of
"http://apache.org/xalan/features/optimize"; then ?
Thanks again
Marc
Henry Zongaro wrote:
Hi, Marc.
Marc Jambert <[EMAIL PROTECTED]> wrote on 2005-07-12
04:44:45 AM:
Henry Zongaro wrote:
It is very specific to a special implementation of DOM that I am writing
for dealing with huge documents (each DOM node is created on demand and
not necessarily kept in memory). I think that the DTM mechanism assumes
that a DOM node will be always the same Java object, which is not the
case for me.
I have already XPath working over my custom DOM with Jaxen and Saxon but
it would be nice if it could work as well with JAXP default
implementation.
That is why would like to disable DTM mechanism. Do you think there is a
solution ?
If you're asking for a way to use the XPath API of Xalan-J without
using DTM, it's not possible without rewriting large parts of the
processor; the implementation of XPath and XSLT in Xalan-J is built upon
DTM.
Joseph Kesselman did some work on a revised DTM implementation over
DOM which, if I recall correctly, does not rely on a DOM node to be always
the same Java object, but I don't believe that work was ever completed. If
you're interested, you can take a look at the code in the xslt20 branch of
the xml-xalan project, in the org.apache.xml.dtm.dom2dtm2 package.
Thanks,
Henry
------------------------------------------------------------------
Henry Zongaro Xalan development
IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044
mailto:[EMAIL PROTECTED]
