I was able to get the transformer working by cutting out the java content
handler.
Thanks for your advice with this.
Gary
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Jan 19, 2007, at 5:15 PM, Joerg Heinicke wrote:
When I put LogTransformer before the custom transformer I can see
logging,
but when it is after the custom transformer there is no logging.
I think
this shows there something wrong with my transformer.
Perhaps it was too simple, but acce
>
> 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 r
On 19.01.2007 23:03, Gary Larsen wrote:
When I put LogTransformer before the custom transformer I can see logging,
but when it is after the custom transformer there is no logging. I think
this shows there something wrong with my transformer.
Perhaps it was too simple, but acceptable in 2.1.7.
> > Initially I wasn't using an updated cocoon.xconf, but the problem still
> > exists. Any ideas how to debug this?
>
> There is a transformer that only logs the sax events: LogTransformer.
>
Thanks for your help.
When I put LogTransformer before the custom transformer I can see logging,
but
On 19.01.2007 22:12, Gary Larsen wrote:
XML Parsing Error: no element found
Location: http://notebook1:8080/netvisn/
Line Number 1, Column 1:
The transformer is processing the sax events but it seems that nothing
is
being delivered back to the pipeline.
It's a parsing error, so I'd guess it'
>
> > XML Parsing Error: no element found
> > Location: http://notebook1:8080/netvisn/
> > Line Number 1, Column 1:
> >
> > The transformer is processing the sax events but it seems that nothing
> is
> > being delivered back to the pipeline.
>
> It's a parsing error, so I'd guess it's not the t
On 19.01.2007 18:58, Gary Larsen wrote:
XML Parsing Error: no element found
Location: http://notebook1:8080/netvisn/
Line Number 1, Column 1:
The transformer is processing the sax events but it seems that nothing is
being delivered back to the pipeline.
It's a parsing error, so I'd guess i
I'm upgrading Cocoon from 2.1.7 to 2.1.10 and having a problem with a custom
Transformer.
This is the error returned in the browser (with XML serializer after the
transformer):
XML Parsing Error: no element found
Location: http://notebook1:8080/netvisn/
Line Number 1, Column 1:
The transformer
