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

[Nicola Ken Barozzi]

Carsten Ziegeler wrote:

Nicola Ken Barozzi wrote:

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

Yes.

[...]

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.

I totally agree with InputModules - and we discussed this already some weeks
ago in the thread about the InputModules Interface. If you look at it, this
interface was not directly intended for the use in the sitemap. So we
should fix this (already discussed, too) as well.

Ok, cool.

Perhaps there is a better name for inputmodules but as I don't want
to start a new thread about "what is the best name". I would like
o.a.c.sitemap.inputmodules.*

Ok, no thread ;-) but if anyone tonight has an illumination about the name, please let us know... :->

Ok, now to the sources... :) - the sources are a configuration on the
application level, you once define which protocols you can use in your
application and that's it. So, the cocoon.xconf is in my eyes the
right place. Furthermore I see some technical problems with declaring
a source in the sitemap.

Now, if you follow this road, that every important aspect has to
be in the sitemap, you can add the xsp logicsheet definitions there
as well, because in the sitemap they are more visible for XSP
developers. And so on.

Actually I always thought that having them in cocoon.xconf was wrong, because it necessarily places them Cocoon-wide. So I would be +1 for it too.

IMHO cocoon.xconf should keep only the Components needed by Cocoon itself, like the store... not developer resources.

So I think we should leave them where they are.

Your logic makes sense.
IMV, but just IMV, Sources should be Components that are always used for Generators. But this actually is probably something that should be done in a revisitation of the Cocoon pipelines:

<map:source src="..."/>
<map:generator/>
<map:transformer/>
<map:serializer/>
<map:sink src="..."/>

This would actually decouple the Generator from the "get the stuff to process" part in a clearly defined way... probably food for thought for Cocoon3, dunno.

Bottom line: let's keep sources Cocoon-wide till we find a compelling use-case, or till we have the decoupled sitemap.xconf working.

--
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]