Scott,
I have now finished the work with removing the temporary
DOM from XSLTC's compiler and removing the few bugs that
followed that work.
Now I want to focus more in Xalan/XSLTC integration, and
I want to start digging into the Xalan code. I still want
to focus on the input/output parts and on the internal DOM.
I have a million (or so) questions:
o) What is your internal DOM - stree or dtm or both?
o) Where can in find some detailed documentation on it?
o) What is the interface between Xalan in the internal tree?
o) Is the tree made up of arrays (such as with XSLTC and
Saxon) or are all nodes object (such as with W3C).
o) Is the database connectivity stuff a part of Xalan or
does it belong with a different project (Cocoon, etc.) ?
o) Where can I read more about this? The design docs are
unfinished, but what is there gives a basic understanding.
There are some parts of XSLTC that I want to stay completely
clear off, as they do not have a functional counterpart in
the original Xalan code.
The most obvious is the compiler. 99% of all classes in the
compiler is used to generate Java bytecodes. Even one such
class may represent an <xsl:for-each> element, it shares no
functionality with the Xalan code that handles the same
element (except for element/attribute parsing).
Parts of the runtime library may have some functional
components that we can share, but other parts are merely
extensions to the translet (or the AbstractTranslet base
class) an very much tied to the compiled code in the translet.
Morten
