Hi Daniel, If you have found any additional information on this, please share. I'm using a BeanEditor right in a simple form and running into the same issue you did.
Thanks, Kevin On 10/23/07 4:49 PM, in article [EMAIL PROTECTED], "Daniel Leffel" <[EMAIL PROTECTED]> wrote: > 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> >> -- Kevin Menard Servprise International, Inc. Remote reboot & power control for network equipment www.servprise.com +1 508.892.3823 x308 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
