cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Helma van der Linden (JIRA)" <j...@apache.org>
Subject [jira] Closed: (COCOON-309) the cocoon:// protocoll allows no modular reuse
Date Tue, 25 Oct 2005 13:26:56 GMT
     [ http://issues.apache.org/jira/browse/COCOON-309?page=all ]
     
Helma van der Linden closed COCOON-309:
---------------------------------------

    Resolution: Fixed

closed with resolution = fixed

> the  cocoon:// protocoll  allows no modular reuse
> -------------------------------------------------
>
>          Key: COCOON-309
>          URL: http://issues.apache.org/jira/browse/COCOON-309
>      Project: Cocoon
>         Type: Bug
>   Components: - Components: Sitemap
>     Versions: 2.0.5-dev (Current CVS)
>  Environment: Operating System: other
> Platform: Other
>     Reporter: Maurice Schoenmakers
>     Assignee: Cocoon Developers Team

>
> The bug prevents in general a modular reuse of a result of an existing sitemap 
> into a new sitemap without having to change the original sitemap.
> Situation: 2 subdirectories /mount/A  /mount/B, each with an own sitemap.xmap. 
> In sitemap A we use the cocoon protocol:
> <map:generate src="cocoon://mount/B/xyz" /> 
> causes as an siteeffect an error that  "stylesheets/y.xsl" can not be found 
> for the following sitemap.xmap B:
> <map:match pattern="xyz">
>     ...
>     <map:transform src="stylesheets/y.xsl"/>
>     <map:serialize/>
> </map:match>
> reason seams to be that the relative url ="stylesheets/y.xsl" of the 
> transformer source in the sitemap B is not resolved relative to the directory 
> of B but releative to the directory of A !!!. (PathInfo for the request of the 
> cocoon: protocol is maybe wrong ???)
> (Only after writing an absolut context url in sitemap B the thing worked. This 
> is a problem as it requires absolute urls every where and the path app B is 
> hard coded in sitemap B ?!?!)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message