Hi Massimo I'm experiencing the same thing. I'm trying to create an editor for properties annotated with "@ManyToOne" The BeanBlockContribution renders ok, but when I submit the form I get an exception:
org.apache.tapestry5.runtime.ComponentEventException Failure writing parameter 'value' of component Editors:caetg: Could not find a coercion from type java.lang.String to type org.apache.tapestry.tutorial.model.Caetg. Available coercions: ..... (you know the rest) As you said It works perfectly fine if I put the same code as a <t:parameter> within the beaneditform I haven't found a solution yet, but I'm looking. Salutti. Alejandro. On Wed, Jun 4, 2008 at 11:28 AM, Massimo Lusetti <[EMAIL PROTECTED]> wrote: > The HibernateEntityValueEncoder (very nice feature!) does not work > properly when needs to look up a property from a PropertyEditContext > from within a BeanBlock contributed to the main BeanBlockSource. > > I mean i got an entity Customers which has a property Provinces which > is another entity. When it comes to BeanEditor it doesn't know how to > render a property of type Provinces so i contribute a BeanBlock to > instruments it how to deal with that data type. > The Provinces property is rendered as a Select so i expect the > HibernateEntytyValueEncoder to encode my Provinces as their own id but > it does not. Contrary if i put a <t:parameter> within the BeanEditor > with the same select as the one from the BeanBlock it does encode the > Provinces entity in the correct way. > > So i guess this has something to do with the PropertyEditContext. Does > anyone have experienced the same behavior? > > -- > Massimo > http://meridio.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
