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]
