Sylvain Wallez wrote:
Thomas Alexnat wrote:
are resulting in a corrupt XML tree after calling them with the
default pretty-print view. As expected, the pretty-view gets
pretty-printed...
Now the question is what behaviour is to be considered "correct"
regarding views and internal pip
Joerg,
thank you for your response. It seems that my problem seems not to be
solved with the current version of cocoon. Is this correct? I am
wondering if this is a bug or a feature. As a cocoon user I would say
this is a MAJOR bug in the view concept or implementation. Should I add
this bug to
On 08.12.2004 11:38, Sylvain Wallez wrote:
Ok, so "cocoon:raw" behaves exaclty as the regular "cocoon:" regarding
views.
QUESTION
What could be the best practice, if I want to look at the XML of a
certain pipeline, before its transformation is being called? All I
need is a good debugge
Thomas Alexnat wrote:
Dear Sylvain,
thank you for your help. I have tested your idea, with a simple
content aggregation and both variants do not show the correct xml tree:
or
are resulting in a corrupt XML tree after calling them with the
default pretty-print view. As expecte
Dear Sylvain,
thank you for your help. I have tested your idea, with a simple content
aggregation and both variants do not show the correct xml tree:
or
are resulting in a corrupt XML tree after calling them with the default
pretty-print view. As expected, the pretty-view get
