The right solution is to implement your own versions of BeanModel and PropertyModel; I think you'll find that much easier than trying to bend the JavaBeans-specific implementations to your needs.
On Wed, Sep 19, 2012 at 4:23 AM, Thiago H de Paula Figueiredo <[email protected]> wrote: > On Wed, 19 Sep 2012 04:02:23 -0300, llama-king <[email protected]> wrote: > >> @Thiago - this is just the issue in that the PropertyModelImpl source >> looks >> like this; >> >> public PropertyModelImpl(BeanModel model, String name, PropertyConduit >> conduit, Messages messages) { >> -- snip -- >> id = TapestryInternalUtils.extractIdFromPropertyExpression(name); >> label = TapestryInternalUtils.defaultLabel(id, messages, name); >> -- snip -- >> } > > > You shouldn't use PropertyModelImpl. Instead, just implement your own > PropertyConduit implementation and add properties to BeanModel using the > add(String propertyName, PropertyConduit conduit) or add(RelativePosition > position, String existingPropertyName, String propertyName, PropertyConduit > conduit) methods. PropertyModelImpl is just for real Java-style properties. > In addition, it's inside a package named 'internal', so it shouldn't be used > directly. > > > -- > Thiago H. de Paula Figueiredo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
