* <p> * To force conversion of property value to a specific type, you can provide * constructor argument 'propertyType'. if that is set, that type is used for * conversion instead of the type that is figured out by * [EMAIL PROTECTED] PropertyResolver}. This can be especially useful for when you have a * generic property (like Serializable myProp) that you want to be converted to * a narrower type (e.g. an Integer). [EMAIL PROTECTED] PropertyResolver} sees an incomming * string being compatible with the target property, and will then bypass the * converter. Hence, to force myProp being converted to and from an integer, * propertyType should be set to Integer. * </p>
That's something the model supported on itself. I don't know how relevant this is currently, but if there is a fix for it, I don't see why we would have to ditch this functionality, especially as it has been in there from almost day 1. Eelco On 4/5/07, Johan Compagner <[EMAIL PROTECTED]> wrote:
but what should it do? what kind of functionality do you think we did loose now? johan On 4/5/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > I don't know if we need it per se, but the functionality used to work, > whereas it doesn't right now. If it's an easy fix, it would be nice to > have back. > > Eelco > > > On 4/5/07, Johan Compagner <[EMAIL PROTECTED]> wrote: > > The PropertyResolver class handles it by looking at the type where it > wants > > to assign call something on. > > So are there cases where we really still need it? > > > > johan > > > > > > On 4/5/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > > > > I just found out that PropertyModel#propertyType isn't being used at > > > all. Can someone please tell me when/ how/ why? > > > > > > Eelco > > > > > >
