Jeff Turner wrote, On 19/06/2003 0.35:
Logging SAX events is best done with the LogTransformer
anyway.
I believe this is the point.
I'll do this tonight if there's no objections.
+1
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discus
Carsten Ziegeler wrote:
Jeff Turner wrote:
I'm not too sure of this commit. The problem is that
AbstractSAXTransformer's
debug-level logging is so verbose that it swamps the debug logs
of its children
with stuff like this:
DEBUG (/forrest/body-index.html): BEGIN endTransformingElement
uri=, nam
Yes, yes, remove this stuff! I'll know if the hooks are being called if I
a) use the right namespace
b) override the hooks methods.
I'm sure these were helpful at one point, but now
David
Carsten Ziegeler wrote:
Jeff Turner wrote:
I'm not too sure of this commit. The problem
Jeff Turner wrote:
>
> I'm not too sure of this commit. The problem is that
> AbstractSAXTransformer's
> debug-level logging is so verbose that it swamps the debug logs
> of its children
> with stuff like this:
>
> DEBUG (/forrest/body-index.html): BEGIN endTransformingElement
> uri=, name=link,
t to false by subclasses with a constructor.
> + * */
> +protected final boolean logSAXEvents;
> +
> +public AbstractSAXTransformer() {
> +this(true);
> +}
> +
> +/** @param logSAXEvents Whether to do a debug-level log for each
rser.createDocument();
Node importNode = resource.importNode(fragment, true);
resource.appendChild(importNode);
Then uses the DOMStreamer to output to Source.
Have I missed something?
There might be a general problem with AbstractSAXTransformer,
because I tried to a fragment containing a
namespace dec
s this possible with AbstractSAXTransformer?
thanks for any help
regards Jeremy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
s this possible with AbstractSAXTransformer?
thanks for any help
regards Jeremy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
