Hi Dave,
Thanks for your reply. I still have some questions:
Look, I'm using XalanTransformer and CompileStylesheet a lot in my code, and
especially for printing a DOM tree into a buffer, and till now I didn't have any
problem with them with all kind of XML, XSL files. I'm using a simple XSL which copy
the entire XML. That XSL is parsed into a DOM_Document etc. and used in transformer
together with any DOM tree and there is no problem. That's the reason why I'm still
thinking that it's something that could work fine.
Another think is that when I'm using the transformer with the some XML, XSL, of
course, parsed into DOMTree is working fine. And with some XML, XSL no, but it's
give me an assertion failed, and if I ignore all the assertion the result is
displayed correctly.
The same think is happend with the compile stylesheet.
I don't know what is inside Xalan but why, when I ignore the assertions like:
node1.isIndexed() == true && node1.isIndexed == true (and all the time is the same
assertion) is working fine?
Excuse me for bugging you, but I have a release soon, and if I don't find a solution
I have a lots of changes to do in my stuff.
Thanks,
Cip
[EMAIL PROTECTED] wrote:
> You're correct. The transformer cannot support a pre-built DOM for
> transformation. We're looking at ways to work around that, but it probably
> won't happen for the next release.
>
> Dave
