Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: forrest-dev@xml.apache.org
Message-ID: <3F324515.9030702@che-che.com>
Date: Thu, 07 Aug 2003 14:24:53 +0200
From: Juan Jose Pablos <cheche@che-che.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.2.1) Gecko/20030311 Debian/1.2.1-10
MIME-Version: 1.0
To: forrest-dev@xml.apache.org
Subject: Re: Where to put components (Re: cvs commit: ...)
References: <20030807025133.85356.qmail@minotaur.apache.org>
 <3F32192E.3080209@che-che.com> <20030807095923.GA392@expresso.localdomain>
 <3F322E3C.1040707@che-che.com> <20030807114604.GB392@expresso.localdomain>
In-Reply-To: <20030807114604.GB392@expresso.localdomain>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Jeff,

Jeff Turner wrote:
> 
> status.xmap does not use any readers, selectors or resources, so why
> should it declare a dependency on any, or define any?
> 

That is what I am asking you!, on your last change, you added more stuff 
  than what I think is needed.

> status.xmap does use generators, transformers and serializers, so there
> should probably be 
> 
> <map:components>
>   <map:generators default="file"/>
>   <map:transformers default="xslt"/>
>   <map:serializer type="html"/>
> <//map:components>
> 
> 

But on the last commit you added as well:

 >     <map:readers default="resource"/>
 >     <map:selectors default="browser"/>

and there are a:

   <map:resources>
   </map:resources>

If there should not be there, let me know and I will removed them.


> I'm not following.  If I see
> 
>   <map:transformers default="xslt"/>
> 
> I know that this subsitemap expects 'xslt' to be defined for it.  Why
> would I redefine it?  If I wanted to, what's wrong with that?
> 

There is nothing wrong with define another transformer, but it is wrong 
if you are going to define the same transformer ( as it happends) 
because that is duplication.

Belive or not, this code produces confusion, it you want to leave as 
documentation then let's use <!-- coments -->. I do not like code that 
does not anything but confuse :-)


> 
> Yes I see that.  For example, if we defined the HTML generator only in
> raw.xmap, and then later moved it to sitemap.xmap, we'd break things.
> However, we could always leave a duplicate definition in raw.xmap.  The
> other way round (moving from sitemap.xmap to a subsitemap) always breaks
> things.  It is still better to start with a limited scope, and then
> expand it if necessary.
> 

The root problem is the way we overwrite sitemap, and the need for users 
to overwrite it.

Can we have an external xml file with all definitions?

Cheers,
Cheche