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


---------------------------------------------------------------------
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]>

Reply via email to