cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Piroumian Konstantin <KPiroum...@protek.com>
Subject RE: [RT]: One step for a minimal Cocoon
Date Mon, 01 Jul 2002 12:59:13 GMT
> From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de] 
> Piroumian Konstantin wrote:
> > > 
> > > For creating a standard use of Cocoon we should provide a 
> > > default sitemap where we define the names of the sitemap 
> > > components. So the file generator has always the name "file" etc.
> > 
> > *All* the components in the root sitemap? The intention of samples
> > refactoring was to move all the sample-specific stuff from the 
> > root sitemap
> > to the samples' to make the root sitemap as much simple as possible.
> > 
> I'm talking about components, this means all the generators,
> transformers, serializers, actions, matchers and selectors which are
> of general use.
> Yes, I'm in favour of putting them in the root sitemap. Why? 
> Because to
> create a standard the usual Cocoon user can rely on.
> We (= the Cocoon commnutiy) define the names for the components,
> we say, that there is a file generator, an xslt transformer 
> etc. So if you
> write an example, you can assume that this standard components with
> exactly these names exist, so a <map:generate type="file" src="..."/>
> works everywhere.
> 
> If we have components which only serve the samples, then they 
> shouldn't
> be declared in the root sitemap but in the samples sub sitemap.

Makes sense. 
So, now we need to define which components are more 'standard' and which are
less. Or which goes into the 'Cocoon 2 Standart Edition' (C2SE) and which
into 'C2EE'. ;)

> 
> 
> > > 
> > > Apart from this component definition the main sitemap should
> > > be empty (perhaps some default views we define), but no
> > > resources and no pipelines, except a generic mount:
> > > 
> > >   <map:pipeline>
> > >     <map:match pattern="*/**">
> > >       <map:mount check-reload="yes" src="{1}/" uri-prefix="{1}"/>
> > >     </map:match>
> > >   </map:pipeline>
> > > 
> > > The root directory of the webapp should only contain the WEB-INF
> > > directory with the libs, web.xml, cocoon.xconf etc and this
> > > sitemap. Nothing else.
> > 
> > What about the 'myapp' directory for a quick start? I 
> envision questions
> > like: "I placed my *.xml and *.xsl files in the root, but I 
> get File not
> > found errors. What's wrong". Or 'myapp' can be concidered a 
> sample?.. 
> 
> Yes, I see it as another sample, because for real development 
> with Cocoon
> you properly will not use 'myapp'.

Agree. Though, it's not a sample, but more like an application template to
start with. Maybe it can be a separate block, something like 'cocoon-myapp'
and those users who need a quick start with XML/XSP/XSLT will download it
separately and use?

Konstantin

> 
> Carsten
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
> 

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


Mime
View raw message