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

[Nicola Ken Barozzi]

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.

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.

org.apache.cocoon.datasources.*

or

org.apache.cocoon.sources.*

and

org.apache.cocoon.inputmodules.*

or

org.apache.cocoon.modules.*

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>



Thus we would have them in blocks; the ones with external dependencies in their own blocks, the others in a single block for each group.


--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------


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