this is just a try to rake up this problem with view labels being
ignored inside a aggregation.
maybe now there is anyone who knows:
is this a bug?
-> is there a workaround?
is this a new implementation of views?
-> how/where should I now place the labels?
thanks.
/Leo
On Wednesday, May 22, 2002, at 09:28 Uhr, leo leonid wrote:
> Hi Sylvain,
> yes, I tried every possible combination. label on <map:aggregate>, on
> <map:part>, on both,... the label just seems to be ignored. I also
> tested those combination on the current
> cocoon/documentation/sitemap.xmap (snippet) => same result.
> ....
> <map:match pattern="*.html">
> <map:aggregate element="site">
> <map:part src="cocoon:/book-{1}.xml"/>
> <map:part src="cocoon:/body-{1}.xml" label="content"/>
> </map:aggregate>
> <map:transform src="stylesheets/site2xhtml.xsl">
> <map:parameter name="use-request-parameters" value="true"/>
> <map:parameter name="header" value="graphics/{1}-header.jpg"/>
> </map:transform>
> <map:serialize/>
> </map:match>
>
> /Leo
>
> On Wednesday, May 22, 2002, at 04:46 Uhr, Sylvain Wallez wrote:
>
>> leo leonid wrote:
>>
>>> me again,
>>> I just noticed that some weeks ago there has been a discussion in the
>>> xml-cocoon-dev-list about future implementations of view labels. But
>>> I didn't find any solution or temporary workaround to get labels
>>> interpreted again inside an aggregation.
>>
>>
>> The main discussion was about branching to the view from the _last_
>> label matching the view and not the first one. But nothing has changed
>> yet. For aggregation, could please try to add 'abel="content" on
>> <map:aggregate> ?
>>
>>> Are there any ideas? It would be great, for creating a search index
>>> of the documentation would be possible again.
>>> thanks
>>> /L
>>>
>>>
>>> On Friday, May 17, 2002, at 09:28 Uhr, leo leonid wrote:
>>>
>>>> I wonder what has been changed concerning the behavior of views (and
>>>> why!)
>>>> Now I get HTML-output where I expect XML (and recently still got).
>>>> May this be the reason why the sample "searching the docs" doesn't
>>>> work anymore?
>>>> It looks like the LuceneIndexer is expecting XML-result from the
>>>> content-view
>>>> but it gets HTML, which it is ignoring.
>>>>
>>>> Example (similar to the cocoon-documentation):
>>>> There is a generator without label ("serverpages-nolabel")
>>>> and a simple view to exit the pipeline and serialize the result as
>>>> XML ("content").
>>>> And the goal is to omit head- and foot-parts and all
>>>> HTML-transformations in content-view
>>>> so that there is only the body-content with filter-3.xsl applied
>>>> within a <site/> root element.
>>>>
>>>> Problem:
>>>> In the following pipeline the final transformation (<map:transform
>>>> src="site2HTML.xsl" />)
>>>> is executed in the content-view. But it should not. Or did I miss
>>>> something?
>>>>
>>>> <map:view from-label="content" name="content">
>>>> <map:serialize type="xml"/>
>>>> </map:view>
>>>> ...
>>>> <map:match pattern="*/body-*/page_*.xml">
>>>> <map:generate type="serverpages-nolabel" src="page-
>>>> geneation.xsp"/>
>>>> <map:transform src="filter-1.xsl" />
>>>> <map:transform src="filter-2.xsl" />
>>>> <map:transform src="filter-3.xsl label="content" />
>>>> <map:transform src="content2HTML.xsl" />
>>>> <map:serialize type="xml"/>
>>>> </map:match>
>>>>
>>>> <map:match pattern="*/*/*.html">
>>>> <map:aggregate element="site">
>>>> <map:part src="cocoon:/{1}/head-{2}/{3}.xml"/>
>>>> <map:part src="cocoon:/{1}/foot-{2}/{3}.xml"/>
>>>> <map:part src="cocoon:/{1}/body-{2}/{3}.xml"
>>>> label="content"/>
>>>> </map:aggregate>
>>>> <map:transform src="site2HTML.xsl" />
>>>> <map:serialize />
>>>> </map:match>
>>>>
>>>>
>>>> Thanks!
>>>> /Leo
>>>>
>>>>
>>>
>>
>>
>> -- Sylvain Wallez
>> Anyware Technologies Apache Cocoon
>> http://www.anyware-tech.com mailto:[EMAIL PROTECTED]
>>
>>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
