Somehow, we're getting Xalan into a strange state, such that transformations are resulting in incomplete results - passing the same input DOM through the same function gives different results. Between the two transformations we're doing a bunch of work with Xerces and Xalan (building up DOMs, transforming, etc.), so we must be somehow putting it into a bad state. Is there any way to somehow put Xalan back into a 'fresh' state? I can unroll all of the XMLPlatformUtils::initialize() calls, but is there anything Xalan-specific?

--
Nick



Reply via email to