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 34112] - VM crash and malfunctions with sitemaps mounts and cocoon:// protocol
Date Tue, 29 Mar 2005 10:53:35 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=34112>.
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=34112





------- Additional Comments From m_rolappe@web.de  2005-03-29 12:53 -------
the stack overflow (crash) is an endless recursion; the reference to
sitemap.xmap in test.xmap is relative to test.xmap's context, so test.xmap
indirectly references itself. replace the reference with an absolute one and the
stack overflow is gone.

one core problem is the processing/environment context. this is supposed to be
something like a path/prefix. now, for example, if you mount
'cocoon://test-dynamic-sitemap/generate-sitemap' the context is
'cocoon://test-dynamic-sitemap/'. the mount triggers a resolveURI of the context
URI. in this testcase that would trigger the following section in sitemap.xmap:

...
      <map:match pattern="">
        <map:read src="index.html"/>
      </map:match>
...

when the context is filesystem based there is no problem, since the resolveURI
just returns a Source corresponding to the context (directory) but in the
cocoon: case the context will either resolve to a resource or throw an exception .


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Mime
View raw message