Which processor to work with JAXP reference implementation?

Subject: Which processor to work with JAXP reference implementation?
From: Brian Young <Brian.Young@xxxxxxx>
Date: Fri, 30 Jun 2000 18:08:22 -0400

A few days ago I posted questions about the feasibility of using the JAXP reference implementation with another "brand" XSL processor, as Sun does not have a production one yet.  It seems that this is the path that I am to go down and I was hoping for some advice.  Thank you very much for the response from my last mail.

Some givens:
The XML parser will be the JAXP reference implementation (parser.jar and jaxp.jar).
The plan is to use DOM, not SAX as the exchange between the parser and the XSL processor.
The XSL processor must be "production", or at least not "beta".  There are concerns about Xalan due to this requirement.

I initially pursued a JAXP/Xalan combo.  The first problem I encountered was trying to provide an input parse tree via DOM and output a result tree to a file (presumably via DTM).  It seems that is a no-no.  So, I switched the output of the transform to go to a DOM and wrote that out.  Though I've been doing XML generation and coded XSLT for a little while, I am new to the guts of how the parser and processor work.  Why is DOM input and non-DOM output a problem?  The second problem I encountered (after switching to DOM output) was that the input DOM was not Xerces DOM (heck, it came from JAXP ;)).  Apparently I must right a liaison to fix this.  Is this a difficult undertaking?  I also read that JAXP only supports DOM lvl 1 whereas Xalan supports DOM lvl 2.  Can that be a problem?

Maybe I'm being dense (and I admit my knowledge in this area is weak), but it seems to me that DOM should be DOM, regardless of where it comes from.  If JAXP outputs DOM shouldn't that be good enough for any processor that can take DOM input?

Has anyone hooked up JAXP to another XSL processor like Xalan or Oracle?  Is there a liaison lying around somewhere that I just haven't found?

And based on the requirements that the XSL processor be as close to "production" as possible, which is considered closest to that state?

Thank you very much for your comments.

   Brian Young

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

Current Thread