Steve,

You're entirely correct.  I didn't look at the API docs properly.  My
apologies.  Thanks for the reply.


Mike....

--- Steve Muench <smuench@xxxxxxxxxxxxx> wrote:
> | Oracle's XML Parser for Java uses a somewhat customized version of 
> | the DOM.  Xalan and XT appear to use standard DOMs, but we'll have 
> | to modify the source classes a little because their pre- and/or 
> | post-processing logic isn't all publicly  accessible.  And, 
> | for several reasons, that's not something with which we're entirely
> | comfortable.  
> 
> This is not true. We fully support the standard DOM interfaces
> as well as provide (in our concrete implementations of
> those interfaces) added value methods that developers
> have asked for like:
> 
>   -> print()         Print a node and its descendants
>   -> selectNodes()   Query node and its descendants using XPath
>   -> transformNode() Transform node and its descendantsusing XSLT
>   -> valueOf()       Evaluate XPath expression with respect to node
> 
> If you parse an in-memory DOM Document, you can 
> transform it using our Oracle XSLT XSLProcessor engine.
> 
> _________________________________________________________
> Steve Muench, Consulting Product Manager & XML Evangelist
> Business Components for Java Development Team
> 
> ----- Original Message ----- 
> From: "Michael Harry Scepaniak" <ihispanic@xxxxxxxxx>
> To: <xsl-list@xxxxxxxxxxxxxxxx>
> Sent: Thursday, February 03, 2000 7:25 AM
> Subject: Feeding DOMs to XSLT Processors
> 
> 
> 
> 
> 
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list