OK, so I've done more digging and although it's not working, I think I know why, but I don't know how to fix it. Please help.
This BeanEditor is being uses as a customer property editor as described in the "Adding New Property Editors" (here http://tapestry.apache.org/tapestry5/tapestry-core/guide/beaneditform.html). I'm using it as a BeanEditor because it's being rendered inside a BeanEditForm on a parent page. After looking at the documentation, I noticed that it mentions that BeanEditor looks for overides in the parent BeanEditForm. I've tried placing the parameter override there, but it is also ignored. What is the proper way to do this? On 10/23/07, Daniel Leffel <[EMAIL PROTECTED]> wrote: > > I realize a BeanEditForm will, but I have a BeanEditor which is ignoring > the parameter blocks and was wondering if this behavior is by design or a > bug. Does anyone know? > > In this code, the parameter block is being ignored: > > <t:BeanEditor t:id="savedSearchForm" object="savedSearchBean"> > <t:Parameter name="itemConditionType"> > <t:label for="itemConditionType"/> > <t:TextField t:id="itemConditionType" value=" > savedSearchBean.itemConditionType" translator="integerTranslator"/> > </t:Parameter> > </t:BeanEditor> >
