Ok. Thanks to all of you. I'll play with the InputModule - it gets me sitemap access which is nice, and you're right - it's a component anyway.
Geoff > -----Original Message----- > From: Christian Haul [mailto:[EMAIL PROTECTED]] > Sent: Thursday, June 06, 2002 4:04 PM > To: [EMAIL PROTECTED] > Subject: Re: Best Practice for shared information lookup? Modules? > > > Geoff Howard wrote: > > Wasn't sure what to call this. > > > > I have a need to make some shared information available to > components. I'd > > It depends where you need this information and what kind of > information > it is. > > If it is simple (small), needed by the sitemap, existing sitemap > components or sitemap components that are general in nature > apart from > the value's source (e.g. request parameters, request > attributes &c), go > for an input module. > > If it is complex (large), needed mainly by other (custom) > components, go > for a component. > > If you don't know, implement the InputModule interface and provide > additional access methods as well :-) It's not really an either or > situation. Afterall, you need a component to implement the > InputModule > interface. And I hope, that it's really simple to implement > to it. It's > just the standardized access methods that set InputModules apart. > > Chris. > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: <[EMAIL PROTECTED]> > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
