so i suppose that calling parent from child without trick is not implemented (maybe in future)
i have in my mind somthing that will be not relative to context for example i'm not sure if my small application's root sitemap will be sub-mounted and in which level in existin cocoon runing instance. so i dont know the full path from context to application's root sitemap. i'll try to find somenthing in input modules maybe!? thanx for your replies --stavros On Tue, 9 Dec 2003, Marco Rolappe wrote: > hi stavros, > > you just have to assure that each sitemap is reachable by a context. > sitemap(1) (I assume it's the root sitemap) is reachable via cocoon://, i.e. > a resource 'foo' in that sitemap/context can be reached via cocoon://foo. > > so what you do now is to make each subsitemap reachable by its parent; let's > name the subsitemaps after the pattern 'ss?'. in the root sitemap you match > on 'ss2' and mount sub-sitemap(2)'s sitemap; > > in sitemap(1): > > ... > <map:match pattern="ss2"> > <map:mount src="ss2/" uri-prefix="ss2"/> > </map:match> > ... > > > you do the same for the other sitemaps. > > > then, for example, from sub-sitemap(4) you can reach resource 'ronin' in > sub-sitemap(2) via 'cocoon://ss2/ronin', and so on. > > > -----Ursprungliche Nachricht----- > > Von: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Auftrag > > von [EMAIL PROTECTED] > > Gesendet: Dienstag, 9. Dezember 2003 09:04 > > An: [EMAIL PROTECTED] > > Betreff: calling pipeline from parent sitemap > > > > > > > > hi people > > > > in my case i have 4 lever sub-sitemap > > > > sitemap (1) > > sub-sitemap (2) > > sub-sitemap (3) > > sub-sitemap (4) > > > > > > the question is how can i use as src in sub-sitemap(4) a pipeline that > > exist in sub-sitemap(3) or (2) ? > > > > i have try cocoon:/ or cocoon:// protocol without success > > > > thanx > > > > -stavros > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
