Could the contributed objects know their names and have space for ordering values (the "before:" and "after:" strings)? In other words, could you simple order the map value() inside your service implementation?
On Wed, May 25, 2011 at 9:42 AM, Kalle Korhonen <kalle.o.korho...@gmail.com> wrote: > 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 > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
