commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject Re: [lang][collections] SortedProperties
Date Tue, 18 Jul 2017 21:37:36 GMT
On Tue, Jul 18, 2017 at 1:16 PM, Oliver Heger <oliver.heger@oliver-heger.de>
wrote:

>
>
> Am 18.07.2017 um 20:39 schrieb Gary Gregory:
> > On Tue, Jul 18, 2017 at 11:25 AM, Rob Tompkins <chtompki@gmail.com>
> wrote:
> >
> >>
> >>
> >>> On Jul 18, 2017, at 4:43 AM, Jörg Schaible <joerg.schaible@bpm-inspire.
> >> com> wrote:
> >>>
> >>> Hi Gary,
> >>>
> >>> Gary Gregory 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
> >>>
> >>> for me it's [collections]. [collections] is like [lang] also an
> >> extension to
> >>> the Java runtime, specialized for the collection/map/array stuff of
> >>> java.util. Especially since we tried to strip [lang] down and have
> >> already
> >>> moved stuff now into more specialized components.
> >>
> >> I'm stuck in the in-between here with the following thought: HashTable
> >> certainly feels like a collection of objects, but it clearly extends
> >> Dictionary and isn't in the collections family. But we are in java.util
> >> here and not in java.lang, so that feels more like it could be in
> >> collections. Plus properties are essentially a map, despite they're
> being
> >> implemented on top of hashtable.
> >>
> >
> > You know what, after scanning the [lang] and [collections] code base, it
> > really seems better in [collections].
> >
> > I'd like to propose
> > org.apache.commons.collections4.properties.SortedProperties.
>
> A heretical question: Is the use case generic enough that such a class
> should be added to Commons?
>
> Most users do not care about the order of properties. And if they do,
> there might be special requirements, e.g. should the order be
> case-sensitive or not, should newly added properties appear at the end
> (keeping the original order), ...
>

Valid question. Take a look at [collections] though. It is full of
variations on different kinds of collections.

Supporting some way of sorting a Properties object seems quite reasonable
in that context.

Gary


>
> Oliver
>
> >
> > Gary
> >
> >
> >>
> >> -Rob
> >>
> >>>
> >>> Cheers,
> >>> Jörg
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >>> For additional commands, e-mail: dev-help@commons.apache.org
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >> For additional commands, e-mail: dev-help@commons.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message