cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Larsen" <>
Subject RE: Problem in custom Transformer (migrating to 2.1.10)
Date Fri, 19 Jan 2007 22:42:19 GMT
> What happens with the decorator? Somewhere it must be set as new content
> handler. Otherwise it would not do anything (also no harm). It would be
> interesting to see if the sax event methods gets called in your
> transformer and later in the decorator. Somewhere they must get lost
> before reaching super.contentHandler.
> Jörg

    public SaxDecorator(ContentHandler contentHandler) {
        this.contentHandler = contentHandler;

>From the application log I can see events are processed in the transformer
and decorator.  

DEBUG 64406 [http-8080-Processor25] SaxDecorator: startDocument called
DEBUG 64406 [http-8080-Processor25] NamespaceDecoratorTransformer:
startDocument() called
DEBUG 64547 [http-8080-Processor25] NamespaceDecoratorTransformer:
startElement() called - uri: loc:userSession raw:userSession
DEBUG 64547 [http-8080-Processor25] SaxDecorator: startElement -
DEBUG 64547 [http-8080-Processor25] NamespaceDecoratorTransformer:
startElement() called - uri: loc:adminLoggedOn raw:adminLoggedOn
DEBUG 64547 [http-8080-Processor25] SaxDecorator: startElement -
DEBUG 64562 [http-8080-Processor25] NamespaceDecoratorTransformer:
startElement() called - uri: loc:appStatus raw:appStatus
DEBUG 64562 [http-8080-Processor25] SaxDecorator: startElement -

I guess I'll look through the change Cocoon change log again.  It's just a
mystery why this works in 2.1.7.  The reason for upgrading was to use the
new XML jars so maybe hat has something to do with it.

Thanks again,

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message