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=35435>. 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=35435 ------- Additional Comments From [EMAIL PROTECTED] 2005-06-21 13:27 ------- I agree with Sylvain (of course) and therefore I have made a different implementation. As Sylvain suggested, the URIPrefix can be obtained through the request input module. This involves a change in the Request interface, so all its implementing classes must be changed as well. The rationale for this proposed change is as follows: The Request (and hence the RequestModule) supports getSitemapURI which gives you the part of the URI that is seen by the sitemap. Thus, if the sitemap is mounted at /a/b, and the requested URI is /a/b/c/d, the sitemapURI is c/d. The URIPrefix complements this, and would be a/b/. It is useful to have the URIPrefix to make absolute links in a HTML document to other pipelines in the same sitemap. This is often difficult when the ** pattern is used in a match, because simple relative links will not work. By using the URIPrefix, one can make sitemaps completely relocatable, i.e., they still work when you change the mount point, if you make relative links absolute by prefixing the URIPrefix. See also the third point in http://www.rabellino.it/blog/index.php?title=things_to_remember_for_the_next_cocoon_p&more=1&c=1&tb=1&pb=1 The getURIPrefix code follows the getSitemapURI code very closely, so I expect that it does not use any APIs which are going to be deprecated soon. The necessary patches have been attached. -- 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.
