cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 28165] New: - recursive map hits result in blank page
Date Fri, 02 Apr 2004 17:54:06 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28165>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=28165

recursive map hits result in blank page

           Summary: recursive map hits result in blank page
           Product: Cocoon 2
           Version: 2.1.4
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: sitemap components
        AssignedTo: dev@cocoon.apache.org
        ReportedBy: martin.a.stangl@siemens.com


If a map is matched at least twice during page generation, it results in a blank
page.

Example:
Imagine following directory structure
root
- sitemap.xmap
- test.xml  
+ sub1
  - sitemap.xmap
  - test.xml
  + sub2 
    - test.xml
    + sub3
    ...

The sitemap.xmap in root contains following map:
...
   <map:match pattern="*.xml">
     <map:generate src="{1}.xml"/>
     <map:serialize type="xml"/>
   </map:match>
...

The sitemap.xmap in sub1 contains a more special map:
...
   <map:match pattern="**test.xml">
     <map:aggregate element="page">
       <map:part src="{1}test.xml" strip-root="true"/>
       <map:part src="cocoon:/{1}../test.xml" strip-root="true"/>
     </map:aggregate>
     <map:serialize type="xml"/>
   </map:match>
...

If I try to get http://localhost:8888/sub1/sub2/test.xml or
http://localhost:8888/sub1/test.xml the result is an empty page.

What I would prefer to happen:
To generate http://localhost:8888/sub1/sub2/test.xml, the file
root/sub1/sub2/test.xml is merged with cocoon://sub1/test.xml.
To do this, cocoon://sub1/test.xml has to be generated first by merging the file
root/sub1/test.xml and cocoon://test.xml.
Cocoon://test.xml is simply providing the file root/test.xml.

Maybe this behavior is meant to be a short circuit protection. In my case a
working recursion would save me a lot of work by not having to create a
sitemap.xml for every subdirectory.

Mime
View raw message