Jan 24th, 2005, 08:33 AM
I was wondering why BeanPropertyAccessStrategy explicitly prevents null domain instances within its BoundValueModel.
I can understand the argument for it (ie. the BeanWrapperImpl needs to know the class type to find BeanInfo), but surely a better way would be to add properties to this class to specify the value class, or even the classes expected down a chained property path?
I can think of a lot of situations where one might want to bind a form to an model with no current domain object (even though the expected type is known), and then have those objects created or queried for in response to user action.