cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: [RT]: InputModules interfaces
Date Tue, 08 Oct 2002 07:55:02 GMT

Christian Haul wrote:
>
> On 08.Oct.2002 -- 08:09 AM, Carsten Ziegeler wrote:
> > So, summarizing this, it seems that we agree on changing the InputModule
> > interface to
> >
> > o.a.c.components.modules.InputModule
> > {
> >    Object getAttribute( String name, Map objectModel ) throws
> > ProcessingException;
> >
> >    Iterator getAttributeNames( Map objectModel ) throws
> ProcessingException;
> >
> >    Object[] getAttributeValues( String name, Map objectModel ) throws
> > ProcessingException;
> > }
> >
> > Everyone happy with this?
>
> Not happy but OK ;-)
>
:(

> Just one thing: Where should the other two interfaces go?
> o.a.c.components.modules.OutputModule
> o.a.c.components.modules.AutoIncrementModule
> then?
>
Hmm, I currently see a use case for the InputModules: in the sitemap
as a better way for getting information than writing custom actions.
It seems that some of you a re using InputModules in other scenarios
as well. So, can you give some more information about where and
why to use OutputModules?
For me, it seems that AutoIncrementModule is very database specific
and if so, it should go to a totally different place.

Carsten


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


Mime
View raw message