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 the bugtracker?
Cheers, Thomas
On 08.12.2004, at 21:18, Joerg Heinicke wrote:
On 08.12.2004 11:38, Sylvain Wallez wrote:
Ok, so "cocoon:raw" behaves exaclty as the regular "cocoon:" regarding views.QUESTIONThe answer with the current view handling is to only use view with "final" pipelines, i.e. ones that don't rely on "cocoon:" URLs.
--------
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 debugger view for any matcher. I am just wondering why nobody else had this same issue before...
Now the question is what behaviour is to be considered "correct" regarding views and internal pipeline calls. Should we consider that view should be taken into account only for external requests?
The current behaviour makes no sense as you can not specify views/labels on the pipeline, but also on the components. Thomas' use case already shows this leads to stupid behaviour as the duplicate usage of a component with @label leads to duplicate usage of view pipe components.
IIRC this behaviour also was different, wasn't it? Wasn't only the last view taken into account if it is multiple times in a pipeline? Why should this behaviour different if an internal pipeline is involved? I would not restrict the usage to external requests as we might break usages of that "feature" - if it is implementable otherwise.
Joerg
Schoene Gruesse, Thomas
