I can't think of a way to do that currently. I mean , you could have a number of components that take a list, and provide a filtered view of that list, and chain it together that way. This might be something better accomplished as a pipeline defined inside the IoC than as components.
On 6/22/07, Dan Adams <[EMAIL PROTECTED]> wrote:
So Lets so component A has a parameter called 'foo' that is required but I would like to be able to just drop in component B and have it provide the value for that parameter on that component. Is there any way to do this? Specifically, I'm trying to design a component that can attach a number of filters to a grid component that will filter the data source before grid renders. So far it would look something like this: <t:cms.gridfilters> ... other filters ... </t:cms.gridfilters> <t:grid source="source"> ... </t:grid> gridfilters would have to somehow get the source used by grid before grid renders. Any way to do this currently? Could this call for a grid enhancement? -- Dan Adams Senior Software Engineer Interactive Factory 617.235.5857 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
