Ron Piterman <rpiterman <at> gmx.net> writes:
>
> If you look at the example in the bug, you can see this isn't working.
> Its not about changing the property or binding it, but about passing a
> parameter to the component which is passed further to the bean.
You're right. The bug seems to be in:
public class BindingBeanInitializer extends AbstractBeanInitializer
{
public void setBeanProperty(IBeanProvider provider, Object bean)
{
if (_binding == null)
//BUG: Because there is only one BindingBeanInitializer for a
//component type, it should NOT cache the binding because the
//binding refers to a specific component.
{
IComponent component = provider.getComponent();
String description =
BeanMessages.propertyInitializerName(_propertyName);
_binding = _bindingSource.createBinding(
component,
description,
_bindingReference,
BindingConstants.OGNL_PREFIX,
getLocation());
}
Class propertyType = PropertyUtils.getPropertyType(bean, _propertyName);
Object bindingValue = _binding.getObject(propertyType);
setBeanProperty(bean, bindingValue);
}
}
--
Author of an e-Book for learning Tapestry (http://www.agileskills2.org/EWDT)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
