My use case is to write a Properties object in sorted key order, nothing fancy. The simplest way is to subclass Properties and override keys().
Loading a SortedProperties with a Map is not on my to-do list. Gary On Jul 18, 2017 00:41, "Javen O'Neal" <one...@apache.org> wrote: > +1 for Lang. > > There aren't any persistent data structures in Collections, nor would I > think to look in Collections to find one. > > Properties is a persistent hashtable. SortedProperties is a persistent > TreeMap. > > Unless you're thinking about a new family of SortedProperties. Were you > thinking about letting the user provide the Map implementation and the > SortedProperties would handle the persistence? > For example, if I wanted to persist a MultiValuedMap or a BidiMap, could I > do that? > new PersistentMap<MultiValuedMap<K, V>>(); > new PersistentMap<CaseInsensitiveKeyedMap<String, Object>>(); > Is there a real scenario where this would be needed? > > On Jul 18, 2017 00:19, "Amey Jadiye" <ameyjad...@gmail.com> wrote: > > > My opinion is this should go to *lang* because the fact is it's extended > > utility and not exactly as data structures though it looks like one. It's > > main purpose is to hold properties and not the data. Commons collection > > aims to provide utlilities and extension to data structures and not to > > properties related utilities. Properties is very basic thing no matter > > it's sorted or not sorted and should go to lang. > > > > Regards, > > Amey > > > > On Tue, Jul 18, 2017, 11:58 AM Gary Gregory <garydgreg...@gmail.com> > > wrote: > > > > > Hi, > > > > > > I'd to have a new class called SortedProperties that extends > > > java.util.Properties. > > > > > > Should that go in [lang] or [collections]? > > > > > > I first thought [lang], but it _is_ a collection after all. > > > > > > Gary > > > > > >
