cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thorsten Scherler (JIRA)" <>
Subject [jira] Updated: (COCOON-2253) StringXMLizable in combination with IncludeXMLConsumer does not handle xml-comments
Date Fri, 27 Feb 2009 12:35:12 GMT


Thorsten Scherler updated COCOON-2253:


Class that will show the error.

Save it where you have your java classes in the directory "org/apache/forrest/dispatcher/transformation".

Please add to your sitemap:
  <map:transformer name="testComment"

and later a debug match like:
<map:match pattern="">
  <map:generate src="SomeXmlDoesNotMatterWhich.xml"/>
   <map:transform type="testComment"/>
   <map:serialize type="xml"/>

You will see 
<?xml version="1.0" encoding="ISO-8859-1"?>

BUT the entrance had been:

> StringXMLizable in combination with IncludeXMLConsumer does not handle xml-comments
> -----------------------------------------------------------------------------------
>                 Key: COCOON-2253
>                 URL:
>             Project: Cocoon
>          Issue Type: Bug
>          Components: * Cocoon Core
>            Reporter: Thorsten Scherler
>            Assignee: Cocoon Developers Team
>         Attachments:
> I encountered a very weird problem that happened suddenly.
> I am using the dispatcherTransformer [1] and in the method structurerProcessingEnd()
I am doing: ... StringXMLizable xml = new StringXMLizable(out.toString()); xml.toSAX(new IncludeXMLConsumer(super.xmlConsumer));
> I as well tried XMLUtils.valueOf(new IncludeXMLConsumer(super.xmlConsumer), xml);
> but after this stage the comments disappear.
> You can test it by doing StringXMLizable xml = new StringXMLizable("<body><!--test--></body>");
xml.toSAX(new IncludeXMLConsumer(super.xmlConsumer)); in a clean transformer and you get "<body>
> First I though it is the RedundantNamespacesFilter which I used as consumer but changing
this did not work.
> I see (while debugging) in the IncludeXMLConsumer that comment(...) is not being called
but does it e.g. for startElements.
> Anybody has a clue what is going on?
> salu2
> [1]

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message