Let's just make sure we're on the same page about beans and components. Each component will, utlimately, have its own instance of the bean.
The bean's required property is set from the component's required property, which itself is a parameter. Each bean is createdon first reference; at which point the corresponding bean's required property is set from the current value of the component's required property. After this initialization, there is no connection between the bean property and the component property. If we agree on this, and you are sure there is an error, then I can pull apart some of the code to see what's up. If this scenario, I'm concerned that the BeanFactory for the component is being shared between instances ... but that's highly unlikely. On 7/15/05, Ron Piterman <[EMAIL PROTECTED]> wrote: > Hi, > > in a component I have a 'required' parameter, which is passed to a > validator bean to use in a "ValidField" component: > > <parameter name="required" default-value="false"> > > ... > > <bean...> > <set name="required" value="required"> > > If i use more than one instance of my component in a page, the bean is > not updated for each instance, thus all are either required or not, > depending on the *first* instance. > > Is this a bug, or should bean properties not be minupulated through > parameters? or maybe it is the result of removing the "direction" > attribute from the parameter definition? > > Cheers, > Ron > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta 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]
