I've implemented my own BeanModel/PropertyModel to allow my pre-tapestry
data model to interact with the BeanEditFrom.  I've run into a roadblock.
When my beanModel returns a property datatype other than text, checkbox or
select,   I'm unable to set the BlockOverride in
BeanEditForm.setParameterName().

For the case at hand, I want to produce a datatype of "crud" which would
(when rendered via BeanEditForm) produce a link to a page where the
parameter can be edited.  I'm thinking that if I can induce Tapestry to use
my own block for non-"primitive" datatypes.  Can others see the utility in
this approach?  Is there someway that I could add a parameter binding to
ComponentResources so that a custom override can be provided?

Thanks, Ki

Reply via email to