Thanks, I'll try this, although it's not as pretty as it could be in otherwise such a great framework...
Looking forward for those resources with inheritance! :) -Tuomo On Fri, 6 Feb 2004, Rottmann, Lars wrote: > > This is exactly what we do, too. We have put our device-dependent stuff into > one resource and saved it in a separate file. This file is included as an > XML entity in the main sitemap and every subsitemap. > > Example (put it right in front of the <map:sitemap ...): > > <!DOCTYPE map:sitemap [ > <!-- "devout.xml" is seperated, so that the contained "devout"- > resource can be made available in sub-sitemaps --> > <!ENTITY devout SYSTEM "devout.xml"> > ]> > > > Include the file in the <map:resources>: > > <!-- "devout.xml" contains device-output resources --> > &devout; > > > You need to do that in every sitemap you use. Although it is not nice it > works. Some kind of inheritance of resources would definitively be > desirable. > > Lars > > > > -----Urspr�ngliche Nachricht----- > Von: Carsten Ziegeler [mailto:[EMAIL PROTECTED] > Gesendet: Freitag, 6. Februar 2004 14:12 > An: [EMAIL PROTECTED] > Betreff: RE: Browser based content in a multi-sub-sitemap system > > > Perhaps not the best idea, but you could use XML entities to include the > resources part. > > HTH > Carsten > > > -----Original Message----- > > From: Tuomo L [mailto:[EMAIL PROTECTED] > > Sent: Friday, February 06, 2004 2:06 PM > > To: [EMAIL PROTECTED] > > Subject: Browser based content in a multi-sub-sitemap system > > > > > > Hi, > > > > Should anyone have a hint, how to do this, please let me know! > > > > I have a site with dozens of sub-sitemaps, for which I need to support > > different client devices (pda, wap etc.). > > > > Each sub-sitemap has pipelines. I need to provide an exit point for > > each pipeline, without replicating it into each of my 100 sitemaps. > > How can I do this? > > > > If I define a resource/view at the parent sitemap, it's not callable > > from the sub-sitemaps. (Not supported by Cocoon). > > > > I then tried generating the sub-sitemaps on the fly (using cocoon://), > > by having the exit point in a separate xml-file and > > cincluding/xincluding it there, but there were strange behaviour by > > Cocoon (Caching didn't work) and I got blank pages etc. Anyway, > > dynamic sitemaps didn't feel like the right way to go. > > > > The other thing I tried was to dynamically substitute @type attribute > > at the serializing stage, but it's not supported either by Cocoon. > > > > Running out of ideas here... :| > > > > -Tuomo > > > > > > > Vodafone Global Content Services Limited > Registered Office: Vodafone House, The Connection, Newbury, Berkshire RG14 2FN > > Registered in England No. 4064873 > > This e-mail is for the addressee(s) only. If you are not an addressee, you > must not distribute, disclose, copy, use or rely on this e-mail or its > contents, and you must immediately notify the sender and delete this e-mail > and all copies from your system. Any unauthorised use may be unlawful. The > information contained in this e-mail is confidential and may also be legally > privileged. > >
