Re: [Proposal] Move Sources and Modules as top-level Cocoon components

[Sylvain Wallez]

Nicola Ken Barozzi wrote:

Sources and Modules are incresingly important in Cocoon, and should be used and documented with more visibility.

Sources are IMHO a fundamental piece in Cocoon, because they separate the retrival of data from the actual generation of SAX events in a Generator.

Agree. Sources allow some of the magical features of Cocoon : retreive a content whatever its source using the same components as files.

Input Modules are equally fundamental, as they give another degree of freedom to the sitemap use-space. Yet they are defined in the xconf and not in the sitemap as other components.

Thus, I propose that input modules and sources have heir place in the org.apache.cocoon.* package space, and that are defined in the sitemap alongside other components, like their parents generators and actions.

+1

org.apache.cocoon.datasources.*

-1 : the word "datasource" is too much related to database stuff.

or

 org.apache.cocoon.sources.*

+1.

I was wondering about the plural "source_s_" considering that most often parckage names are singular. IMO, in this particular case it makes sense, since it is a collection of Cocoon-specific implementations of an interface defined elsewhere (in Excalibur).

and

 org.apache.cocoon.inputmodules.*

or

 org.apache.cocoon.modules.*

+1. Wondering also about plural here. But it's also OK, becaus we will have "input", "output" and "inputoutput" subpackages.

Also:

<map:components>
  <map:sources default="file"></map:sources>
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  <map:generators default="file"></map:generators>
  <map:transformers default="xslt"></map:transformers>
  <map:readers default="resource"></map:readers>
  <map:serializers default="html"></map:serializers>
  <map:matchers default="wildcard">  </map:matchers>
  <map:selectors default="browser">  </map:selectors>
  <map:modules default="defaults"></map:modules>
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  <map:actions>  </map:actions>
  <map:pipelines default="caching">  </map:pipelines>
 </map:components>

+1.

<map:components> is getting bigger and bigger, and often bigger than <map:pipelines> itself. So what about allowing it to be in a separate file :
<map:sitemap>
<map:components src="sitemap.xconf"/>
<map:pipelines>
....
</map:pipelines>
<map:sitemap>

This can also be a first step towards the future structure of blocks.

Sylvain

--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]