Seems ok with me if you have a use case for it, even if it just makes tests cleaner.
Gary On Nov 10, 2016 4:55 AM, "Mikael Ståldal" <mikael.stal...@magine.com> wrote: > Would it make sense to have a removeAll(Iterable<String>) method in > ThreadContext, as a companion to putAll(Map<String, String>)? > > And a corresponding method in ThreadContextMap2, which can be implemented > in an atomic way similarly to putAll. > > -- > [image: MagineTV] > > *Mikael Ståldal* > Senior software developer > > *Magine TV* > mikael.stal...@magine.com > Grev Turegatan 3 | 114 46 Stockholm, Sweden | www.magine.com > > Privileged and/or Confidential Information may be contained in this > message. If you are not the addressee indicated in this message > (or responsible for delivery of the message to such a person), you may not > copy or deliver this message to anyone. In such case, > you should destroy this message and kindly notify the sender by reply > email. >
