Joseph Kesselman wrote:
equivalent to asking whether you should use SAX or Xerces.
Again, your not comparing "like with like"
That's what I was saying; you just distilled it a bit better. <smile/>
I've not gotten too far under the hood of the transformer
implementations to know what extra capabilities are available in Xalan,
I think it has a few custom JAXP features for optimization and previewing.
One area I have worked with is Java Extensions. I've written a number of
Extensions in Java for Saxon to integrate it into the Servlet API and
make the Servlet engine functionality (context, request, response,
session) available with stylesheets. I've also written a JNDI directory
Extension. I haven't done either of these yet for Xalan as I haven't
needed it and I'm not too familiar with Xalan's extension mechanism. (I
think Coccon has an Extension for Xalan that does this).
Another area I've been looking at is the DOM level 3.0 functionality
thats getting introduced into Xerces. Specifically in the area of
Accessing schema/validation info for a DOM node.
I'd be curious if the Transformers of the future might make this kind of
information available to in the XSLT developers for more powerful
rendering. Like say, to control rendering of HTML content the user might
use to add elements/attributes to a document based on the valid elements
and attributes that can be added to a document at that point. Not that
the transformer would add the elements/attributes. But that the info
could be useful for rendering forms for editing the underlying content
of an XML file on a server or in a Database...
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list