> setObject() is not supported on LoadableDetachableModel because it extends > AbstractReadOnlyModel. > What is the reason for this?
Because load is an algorithm to get the value; if you set the value you have two different ways of getting that value which gets inconsistent easily. > This way LoadableDetachableModel cannot be used with form controls. Why not? Typically, you would let the LDM return the form object - e.g. a User - and you let individual components work on it's properties - e.g. firstName -. You never need to set the actual user object. > In my case I have a DropDownChoice with a list of non-serializable objects. > What kind of model could I use to store the selected object? The model that provides the possible choices is different from the actual choice. The list could be done with the LDM and the choice e.g. with a property model. Also note that LDM, as convenient a class as it is, is really simple. If you want it to behave differently, it is trivial to create your own kind of model that does what you want. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
