Am 17.08.2013 22:07, schrieb Oliver Heger: > I am currently trying to implement generic conversion methods (as they > already exist in DataConfiguration) in AbstractConfiguration to make > conversion available for all configurations. > > This works in principal. However, when I try to implement the existing > getList() method by delegating to the new generic list conversion method > I discovered some inconsistent behavior of this method. > > The documentation says that this method returns a list of strings. This > is not true; if the list contains itself complex objects, these objects > are returned in the result list. (In contrast, the generic list > conversion method recursively flattens the result list.) There are even > tests which test this behavior; it is used by the property list > configurations to represent nested arrays. > > I am not sure how to proceed here. I see the following options: > 1) Leave this method as it is, but document the behavior. > 2) Change the method to be a thin wrapper over the generic list > conversion method which returns a List<String>. > > My preferred option would be 2), but then it might be necessary to > change the property list configurations to handle nested arrays in a > different way. (Maybe add a special getList() implementation here?) > > Any opinions? > Oliver >
On a second thought, I guess I will not change the getList() implementation, but only tweak its documentation. This has the least effort. Currently, I don't have any itch to manipulate the property list configurations. Oliver > --------------------------------------------------------------------- > 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]
