[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Path/XSLT processor - DOM Input

• To: "'xml-dev@l...'" <xml-dev@l...>
• Subject: Re: Path/XSLT processor - DOM Input
• From: Petr Cimprich <petr@g...>
• Date: Tue, 03 Sep 2002 15:00:42 +0200
• References: <20020903044742.66033.qmail@w...>
• User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827

To generalize my answer to your similar question in sablist:

XPath/XSLT processors usually accept "DOM trees" created with the same 
toolkit. For C/C++ engines, Xalan C++ accepts Xerces's trees, libxslt 
accepts libxml's trees, and Sablotron accepts Sablotron/DOM trees.

Then, you can of course translate an "unknown tree" to the one your 
processor understands to. This requires to scan a tree node by node and 
to build a new tree; it wouldn't be too efficient.

Moreover, with Sablotron and its SXP interface you can work with 
"virtual" trees that can be mapped e.g. to unknown DOM trees. The 
difference from the previous approach is that you don't touch all nodes 
but only those really needed for your transformation/query.

Regards,
Petr


nirmalts wrote:

>Hi,
>
>Is there any XPath/XSLT processor (C/C++) available,
>which accepts a DOM tree as input?
>I know one - Xalan-C++ - but the Xalan performance is
>poor with DOM input. Any other processors?
>
>Nirmal
>
>__________________________________________________
>  
>

-- 
Petr Cimprich
Ginger Alliance
www.gingerall.com

• References:
  • Path/XSLT processor - DOM Input
    • From: nirmalts <nirmalts@y...>

• Prev by Date: OASIS TC Call For Participation: LegalXML Legislative TC
• Next by Date: Re: is xml schema bad wrt schema extensions?
• Previous by thread: Re: Path/XSLT processor - DOM Input
• Next by thread: is xml schema bad wrt schema extensions?
• Index(es):
  • Date
  • Thread