DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9736>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9736 the cocoon:// protocoll allows no modular reuse Summary: the cocoon:// protocoll allows no modular reuse Product: Cocoon 2 Version: Current CVS Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: sitemap components AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] 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 ?!?!) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
