Hi Cip,
> 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?
This assertion just means that you're using the wrong DOMSupport
implementation. If you use the XalanSourceTreeParserLiaison, then use a
XalanSourceTreeDOMSupport instance. If you use the XercesParserLiaison,
use a XercesDOMSupport instance. If you're using XalanTransformer, then it
will create a XalanSourceTreeDOMSupport instance, which is why you can't
use a DOM_Document wrapped as a XalanDocument with XalanTransformer.
Unless you have some reason to parse the document yourself, you can just
let XalanTransformer do the parsing as it transforms.
The latest XalanTransformer code has two new major features. One is that
it allows you to pre-parse a document to using either Xalan's proprietary
source tree, or a Xerces DOM_Document. You can then use that document
multiple times. The other is a "dynamic document builder", which allows
you to build a document through SAX2 events.
> 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
No problem!
Dave
Ciprian
Ungureanu To: [EMAIL PROTECTED]
<cungurea@dyn cc: (bcc: David N Bertoni/CAM/Lotus)
asty.com> Subject: Re: XalanTransformer problem
06/28/2001
11:12 AM
Please
respond to
xalan-dev
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
