From: "Carsten Ziegeler" <[EMAIL PROTECTED]> > Hi, > > I really want to make a decision about the input modules, so that we can > say: "This area is finished." > > Although I'm the (only?) one who thinks that the current InputModules are > not the correct approach for use in the sitemap (as I explained often > enough), I guess the only solution is the most pragmatic one: > > We simply move the definition of the current InputModules into an own > section of the sitemap and that's it. The current implementation is > capable of all required features but has (in my eyes) a not so appropriate > interface. We cannot change this interface for compatibility reasons > and defining a new interface (= new component) is not what we as > a community want. > > What do you think about it?
IMO, most of the users would not like to configure input modules in the sitemap if we provide a good enough set of preconfigured modules for accessing request, session properties and attributes, application context attributes and several others (i18n, xmlsource, sys-property, etc.). What is more required (and thus more important), but probably is a little out of context of this thread, is the syntax used to access input modules in the sitemap. Current approach does not allow to use one value as an input to another input module. Real life use-cases can be found in Cocoon Users list. > > If noone disagrees, could someone do the move? I will then remove my > proposal from the source tree. I am -0 for moving input modules into the sitemap, but if we agree to move then why not call them sitemap variables? E.g.: <map:variable name="request" src="org...RequestModule" /> Variable is a good name for JXPath-enabled input modules and they act very similar to XSLT variables. > > Please, let's come to a conclusion to avoid an over-discussion of this > topic. > And we really need the definition in the sitemap and not the cocoon.xconf. Those, who create or customize input modules have no problems with editing cocoon.xconf for their needs. Having yet another component declaration in the already overloaded sitemap is not a good idea. All IMP, of course. -- Konstantin > > Carsten > > Carsten Ziegeler > Open Source Group, S&N AG > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
