I can certainly play with this solution - Do I need to define the role anywhere else? I had thought there was a ?.roles file somewhere.
This sounds a lot like Input Modules though - have I totally misunderstood them? Congrats on the approval for comitting by the way. Geoff Howard > -----Original Message----- > From: Peter Royal [mailto:[EMAIL PROTECTED]] > Sent: Thursday, June 06, 2002 11:51 AM > To: [EMAIL PROTECTED] > Subject: Re: Best Practice for shared information lookup? Modules? > > > On Thursday 06 June 2002 11:45 am, Geoff Howard wrote: > > I thought of defining a singleton class with public > > getSubsiteID(page-layoutID) methods, etc. but thought there > was a more > > "cocoon" way of doing this that would make the availibilty > more general. > > There is, create a new component! > > Define a role (interface) and your generators/actions can > then implement > Composable and you can then do componentManager.lookup() to > retrieve the > component. > > Add your custom component to cocoon.xconf ala: > > <component-instance class="your.class" role="your.role"/> > > -pete > > -- > peter royal -> [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]> > --------------------------------------------------------------------- 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]>
