No, TraceListen uses the Xalan source tree -- but the classes that you
would substitue to use the Xerces DOM are similarly named. Is it really
that hard to figure out?
Use:
XercesDOMSupport
XercesParserLiaison
instead of:
XalanSourceTreeDOMSupport
XalanSourceTreeParserLiaison
Dave
"Bryan
Mulvihill" To: <[EMAIL PROTECTED]>
<bryan@amconres cc: (bcc: David N Bertoni/CAM/Lotus)
earch.net> Subject: Re: DOM Input woes
09/04/2001
05:35 PM
Please respond
to xalan-dev
The usage pattern doc was what I was using. Unfortuneatly it stops after
the XSLTInputSource. The TraceListen sample doesn't use a Xerces DOM so
mixing the two has given mysterious crashes and I'm not sure as to what
does
what. If anybody has working Xerces DOM conversion, then I would like to
see it.
>
> You can still transform a Xerces DOM instance dynamically, you just can't
> use a XalanTransformer instance to do it.
>
> If you're using the internal APIs, then nothing changes. The TraceListen
> sample still uses the internal APIs, so you can look there for
information
> on how to use those APIs. You can also see this usage pattern which is
in
> the doc for more information on how to substitute the Xerces DOM for our
> source tree:
>
> http://xml.apache.org/xalan-c/usagepatterns.html#dom
>
> Dave
>
>
>
>
> "Bryan
> Mulvihill" To:
<[EMAIL PROTECTED]>
> <bryan@amconrese cc: (bcc: David N
Bertoni/CAM/Lotus)
> arch.net> Subject: DOM Input woes
>
> 09/04/2001 01:30
> PM
> Please respond
> to xalan-dev
>
>
>
>
>
> I am trying to transform a xerces DOM that is created dynamically, but
> after going through the archieves, it appears that this cannot be
> accomplished in ver.1.2.
>
> Is there a way to serializer my DOM and pass that to xalan? If so, can
you
> give a small code sample?
>
> Can a Xalan DOM be generated dynamically and then transformed? If so, can
> you give a small code sample?
>
> Any help would be much appreciated.
>
> Bryan Mulvihill
> Software Developer
> AMCon Research Inc., Ottawa, Ontario, Canada
> http://www.amconresearch.com
>
>
