Major bug with cocoon views -- Using views not really possible

[Thomas Alexnat <th...@alexnat.de>]

Dear Vadim,

I also think, that this behaviour is a bug. To me it renders the usage 
of the cocoon view concept absolutely useless. My major point is, that 
is, that I cannot use the cocoon views to view my current matcher in 
XML. If I try to do that, everytime I have a 'aggreate' or 'cocoon:/' 
protocol in my pipeline, the XSL scrambles the content, because 
previous matchers are also transformed. (see older mails from me)

The only workaround I currently know, is to generate the XML content in 
my own pipie -- not using views. This is not a feature to me, its more 
a big bug.

Where can I add this bug? Or to whom can I talk?

Thanks in advance,
    Thomas



On 10.12.2004, at 14:09, Vadim Gritsenko wrote:

> Sylvain Wallez wrote:
>> Thomas Alexnat wrote:
>
> <snips/>
>
>>> <map:aggregate element="categoryindexpage">
>>>    <map:part src="cocoon:/getXMLContentA"/>
>>>    <map:part src="cocoon:/getXMLContentB"/>
>>> </map:aggregate>
>>>
>>> are resulting in a corrupt XML tree after calling them with the 
>>> default pretty-print view. As expected, the pretty-view gets 
>>> pretty-printed...
>
> <snips/>
>
>> 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?
>
> That would not be correct too, me thinks. Correct behavior would be to 
> "reset" view when making internal request, but allow requestee to 
> specify which view of internal pipeline it desires to obtain.
>
> I mean, example above should work as expected: no view label should be 
> passed to cocoon:/getXMLContentX, but view label should be passed if 
> request is made as cocoon:/getXMLContentX?cocoon-view=content.
>
> Current behavior seems like a bug, and because of this there is no 
> need to preserve it for "backward compatibility".
> ... Hmmm, interesting, when this bug was introduced? ...
>
> Vadim
>
>
Schoene Gruesse,
    Thomas

Re: Major bug with cocoon views -- Using views not really possible

[Ralph Goers <Ra...@dslextreme.com>]

Joerg Heinicke said:
> On 10.12.2004 15:13, Thomas Alexnat wrote:
>> Where can I add this bug? Or to whom can I talk?
>
> You are already talking to *us*, the Cocoon community. Though there are
> people who know more about the internals of Cocoon (sitemap, request
> processing) it is always a community thing and most of committers will
> read this list and so know about this issue. You might add it to
> bugzilla though so that it won't get forgotten. But there is no
> guarantee to get it fixed quickly.

Although it helps when a patch is provided!

Re: Major bug with cocoon views -- Using views not really possible

[Thomas Alexnat <th...@alexnat.de>]

Thank you -- I have submitted a new "ugreport (#32650) hope this will 
be fixed anytime... ;)


On 10.12.2004, at 18:33, Joerg Heinicke wrote:

> On 10.12.2004 15:13, Thomas Alexnat wrote:
>
>> I also think, that this behaviour is a bug. To me it renders the 
>> usage of the cocoon view concept absolutely useless. My major point 
>> is, that is, that I cannot use the cocoon views to view my current 
>> matcher in XML. If I try to do that, everytime I have a 'aggreate' or 
>> 'cocoon:/' protocol in my pipeline, the XSL scrambles the content, 
>> because previous matchers are also transformed. (see older mails from 
>> me)
>> The only workaround I currently know, is to generate the XML content 
>> in my own pipie -- not using views. This is not a feature to me, its 
>> more a big bug.
>> Where can I add this bug? Or to whom can I talk?
>
> You are already talking to *us*, the Cocoon community. Though there 
> are people who know more about the internals of Cocoon (sitemap, 
> request processing) it is always a community thing and most of 
> committers will read this list and so know about this issue. You might 
> add it to bugzilla though so that it won't get forgotten. But there is 
> no guarantee to get it fixed quickly.
>
> Joerg
>
>

Re: Major bug with cocoon views -- Using views not really possible

[Joerg Heinicke <jo...@gmx.de>]

On 10.12.2004 15:13, Thomas Alexnat wrote:

> I also think, that this behaviour is a bug. To me it renders the usage 
> of the cocoon view concept absolutely useless. My major point is, that 
> is, that I cannot use the cocoon views to view my current matcher in 
> XML. If I try to do that, everytime I have a 'aggreate' or 'cocoon:/' 
> protocol in my pipeline, the XSL scrambles the content, because previous 
> matchers are also transformed. (see older mails from me)
> 
> The only workaround I currently know, is to generate the XML content in 
> my own pipie -- not using views. This is not a feature to me, its more a 
> big bug.
> 
> Where can I add this bug? Or to whom can I talk?

You are already talking to *us*, the Cocoon community. Though there are 
people who know more about the internals of Cocoon (sitemap, request 
processing) it is always a community thing and most of committers will 
read this list and so know about this issue. You might add it to 
bugzilla though so that it won't get forgotten. But there is no 
guarantee to get it fixed quickly.

Joerg