cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gerald Aichholzer <ga...@iicm.edu>
Subject Re: directory-independant Coocon applications
Date Sat, 28 May 2005 08:12:37 GMT
Hello Volkmar,

Quoting "Volkm@r" <plsdontreply@arcor.de>:

 > Volkm@r wrote:
 >> What about using absolute url instead of a relative one?
 >> <img src="/global/images/logo.png"/>
 >
 > Sorry Gerald, I should have read your posting more carefully.
 > I've had a similar problem some time ago and the only solution I could
 > find was using *src="../../and-so-on"* generated by a relatively
 > complicated XSLT.
 >

thank you for your infos. AFAICS there are two options available:

1) The application works with absolute URLs. In this case you will
    have to touch the root-Sitemap of an existing Coocoon installation
    and add a pipeline as follows:

    <map:match pattern="url/to/my/app/**">
      <map:mount src="my/apps/dir/sitemap.xmap"
                 uri-prefix="url/to/my/app/"/>
    </map:match>

2) Cocoon's root sitemap uses auto-mounting of sub-sitemaps, i.e.

     <map:match pattern="*/**">
       <map:mount check-reload="yes" src="{1}/" uri-prefix="{1}"/>
     </map:match>

    In this case your application cannot use absolute paths because
    it won't now the uri-prefix. The advantage is that your won't
    need to modify Cocoon's root sitemap.

    The disadvantage is that you will have to use relative paths in
    your application (as you have shown above).


I am looking for a solution which combines both advantages: no need
to modify the root sitemap (if my application is added) and don't
have to use relative paths (i.e. src="../../image/logo.png").

Gerald

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message