[
https://issues.apache.org/jira/browse/COCOON-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Kossakowski closed COCOON-2060.
----------------------------------------
Resolution: Won't Fix
The problem you describe will be fixed in Cocoon 2.2 but not the way you
describe it. In Cocoon 2.2 we have better concepts and techniques than
<map:resource/> from Cocoon 2.1 that was a hack, actually.
In Cocoon 2.2 reusable portions of pipelines will be handled by sitemap (or
servlet) services and postable source. It's our high priority goal so you can
expect to see it implemented very soon. In fact, really basic (and not tested
yet) implementation is already there. Check COCOON-2046 (and COCOON-2050)
issues to get more information about the idea and implementation advance.
I set "Won't Fix" because for resources from Cocoon 2.1 this issue will not be
fixed.
> Call resource in parent sitemap
> -------------------------------
>
> Key: COCOON-2060
> URL: https://issues.apache.org/jira/browse/COCOON-2060
> Project: Cocoon
> Issue Type: Improvement
> Components: - Components: Sitemap
> Reporter: robert.onslow
>
> It is possible to access components in a parent sitemap from a sub-sitemap,
> but not to map:call a resource in the parent sitemap.
> This is preventing me from writing relocatable sub-sitemaps which can call
> back resources in the parent sitemap. Is there going to be a fix?
> See also http://wiki.apache.org/cocoon/FixMe
> Robert
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
