Bruno Dumon wrote:
On Thu, 2003-09-04 at 06:51, Christopher Oliver wrote:
My original intention in "evaluating" the DOM object was to support the
macro factility in JXTemplate. But in its current state the macro
facility is pretty much useless.
Why exactly useless? I haven't used it yet
On Thu, 2003-09-04 at 06:51, Christopher Oliver wrote:
> My original intention in "evaluating" the DOM object was to support the
> macro factility in JXTemplate. But in its current state the macro
> facility is pretty much useless.
Why exactly useless? I haven't used it yet but is seems like som
My original intention in "evaluating" the DOM object was to support the
macro factility in JXTemplate. But in its current state the macro
facility is pretty much useless. So I'm +1 on removing
completely and changing the code to simply stream DOM objects as SAX
events. Do you want to make that
I'm using JXTemplateGenerator (very nice stuff BTW), and remarked that
if the result of an expression is a org.w3c.dom.Node, it will again be
"executed", i.e. parsed as a JXTemplate and interpreted.
I'd like to be able to disable this behaviour, on the one hand because
the data might contain seque
