DO NOT REPLY [Bug 34132] - Source resolving when root sitemap is not in context://

[bu...@apache.org]

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=34132>.
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=34132





------- Additional Comments From m_rolappe@web.de  2005-03-29 12:17 -------
the source resolving is not the problem. the question is whether handing the
TreeProcessor a different path to its sitemap.xmap implies that all relative
references in that sitemap are relative to that sitemap.xmap's directory, i.e.
whether it changes the 'context'. a proper definition of the latter would
propbably help.

the current situation is (tested 2.1.7):
- you can direct (the root) TreeProcessor to use a sitemap.xmap which is not in
the root context directory. this is merely a TreeProcessor configuration thing
and its only side effect is to read the sitemap from a different location. no
influence on other processing like source resolving, etc.
- CocoonServlet (.getEnvironment()) sets the root context of the request
currently being processed to the path/URL of the servlet context, not to the
path of the root sitemap. and this is the reason why all relative references in
the root sitemap are relative to the path/URL of the servlet context.

the core processing (and the 'context' thing especially) should be
reinvestigated and thought through since this might also have influence on
blocks, etc.


-- 
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.