Justin Deoliveira a écrit :
> * ComplexAttribute.getValue() to List
>
> +1 on this one. A list is still more useful even if you are telling
> people that the order in the list may be random.
The only comment I could make on this feature review is related to collections.
I have the feeling that many peoples love java.util.List and don't like the
other collection interfaces... On a pure "principles" point of view, if the
order is not relevant, I would be tempted to suggest to stick to
java.util.Collection. I would like to know why peoples find List so much more
convenient? Is it because it provides a way to avoid the additional verbosity of
using an Iterator? If so, could the new Java 5 language features make it easy
enough to solve this issue?
Andrea Aime wrote (from the PDF document)
> I don't see how casting down getProperties() to Set<Property> does any
> good at explaining better than only a single attribute can be chosen.
> Collection<Property> or List<Property> would be the same, the check
> should be put in a restriction filter and is otherwise
> explained only in the javadoc of the class.
If the properties is expected to contains only singletons, I find nice to
publish that as an explicit Set interface. Is there any reason why a user would
like to access a property by index?
We had a similar issue in GeoAPI metadata; some methods returning Number were
changed to Double because users wanted to publish the expected "kind" of number,
even if it adds nothing on an API point view.
Martin
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
