Edward,
with SAX output one of three classes can get involved:
ToXMLSAXHandler
ToHTMLSAXHandler
ToTextSAXHandler
If Xalan "knows" from the <xsl:output> method attribute what the output
type is, we take advantage of that.
For example the ToTextSAXHandler will pretty much ignore
startElement/endElement calls, and this is an optimization earlier on in
output chain.
I can't remember exactly what, but ToXMLSAXHandler and ToHTMLSAXHandler
also differ. If you are providing your own ContentHandler implementation
then there is a conversion from SAX-like to SAX method calls going on here
with one of the 3 classes mentioned above. Without more information on what
your anomalous behavior is, and what your set-up is, I can't say more.
----------
Brian Minchau
XSLT Development, IBM Toronto
e-mail: [EMAIL PROTECTED]
"Edward L. Knoll"
<[EMAIL PROTECTED]
dex.com> To
[EMAIL PROTECTED]
12/16/2004 10:47 cc
AM
Subject
Other concurrency issues ....
Please respond to
xalan-dev
While we appear to have resolved our two biggest concurrency issues, I
still have a couple of lingering problems I'm trying to
characterize/isolate.
Does anyone know of any concurrency problems related to the XSL
extension mechanism for accessing/calling Java classes/methods? We're
accessing a class we've demonstrated to be thread safe in another
context. We're accessing that class through a wrapper, so the problem
could be there although I currently can't see it.
Even using our own HTML serializer, we're getting some anomalous output
in the final HTML. Does anyone know whether a <xsl:output ...>
statement in the stylesheet is going to have any affect on the XSL
processing (using a SAX TransformHandler) if we don't have a standard
(HTML) Serialize in our SAX processing chain?
--
Edward L. Knoll Phone (FedEx) : (719)484-2717
e-mail (FedEx) : [EMAIL PROTECTED]
e-mail (personal) : [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
