Return-Path: <pati_giacomo@yahoo.com>
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 48105 invoked from network); 19 Jul 2000 06:53:42 -0000
Received: from web6203.mail.yahoo.com (128.11.22.114)
  by locus.apache.org with SMTP; 19 Jul 2000 06:53:42 -0000
Message-ID: <20000719065342.17565.qmail@web6203.mail.yahoo.com>
Received: from [198.240.213.30] by web6203.mail.yahoo.com;
 Tue, 18 Jul 2000 23:53:42 PDT
Date: Tue, 18 Jul 2000 23:53:42 -0700 (PDT)
From: Giacomo Pati <pati_giacomo@yahoo.com>
Reply-To: giacomo.pati@pwr.ch
Subject: Re: Sitemap mount concerns
To: cocoon-dev@xml.apache.org, giacomo.pati@pwr.ch
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

Hi all

Maybe I've bothered you too much with implementational detail. Please
forget my previous mail and respond to this instead.

Let step back to a conceptional view of the sitemap. What fits best
your needs concerning mounts of sub sitemaps. This

  ...
  <map:pipelines>
   <map:pipeline>
    <map:match pattern="dist/*">
     <map:mount src="./dist/{1}"/>
    </map:match>
    <map:match pattern="bugs/*">
     <map:mount src="jar://apps/bugs.cocoon#{1}"/>
    </map:match>
   ...

or 

  ...
  <map:mounts>
   <map:mount uri="dist/cocoon" src="./dist/cocoon"
reload-check="yes"/>
   <map:mount uri="dist/xalan" src="./dist/xalan" reload-check="yes"/>
   <map:mount uri="dist/foobar" src="./dist/foobar"
reload-check="no"/>
   <map:mount uri="bugs/cocoon" src="jar://apps/bugs.cocoon"/>
  </map:mounts>
  ...

The first examples gives the freedom to spread the mount elements all
over the pipelines and have the uri which they are mounted on
wildcarded (this means you don't really know where they are mounted
on).

The second example removes the mount element from the pipelines and
have them centralized in one place in the sitemap. You also exactly see
where they are mounted on.

I don't see the need for the flexibility the first example gives. The
second example reduces verbosity of the pipeline and separates the
concern of mounting to a central place in the sitemap.

I will suggest using the second example.

And you?

Giacomo

=====
--
PWR GmbH, Organisation & Entwicklung      Tel:   +41 (0)1 856 2202
Giacomo Pati, CTO/CEO                     Fax:   +41 (0)1 856 2201
Hintereichenstrasse 7                     Mailto:Giacomo.Pati@pwr.ch
CH-8166 Niederweningen                    Web:   http://www.pwr.ch

__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail � Free email you can access from anywhere!
http://mail.yahoo.com/