I have a use case where I'd like to contribute key-value pairs but preserve their ordering, i.e. I'd like to contribute elements to a LinkedHashMap. Now, MappedConfiguration doesn't work since it doesn't preserve the order (or in Tapestry terms, cannot be ordered after elements are contributed). OrderedConfiguration would work (at least for my use case) if I had an access to the ids of the contributed elements. Would it be a complete heresy, if instead of a List, you could optionally specify a LinkedHashMap (or a custom Tapestry type for an immutable linked map)? Any better ideas for it?
Kalle --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
