ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colm O hEigeartaigh (JIRA)" <>
Subject [jira] [Resolved] (WSS-642) Use LinkedHashSet instead of TreeSet within getInclusivePrefixes
Date Mon, 28 Jan 2019 10:49:00 GMT


Colm O hEigeartaigh resolved WSS-642.
    Resolution: Fixed

> Use LinkedHashSet instead of TreeSet within getInclusivePrefixes
> ----------------------------------------------------------------
>                 Key: WSS-642
>                 URL:
>             Project: WSS4J
>          Issue Type: Improvement
>          Components: WSS4J Core
>    Affects Versions: 2.2.2
>            Reporter: Joseph Athman
>            Assignee: Colm O hEigeartaigh
>            Priority: Minor
>             Fix For: 2.2.3
> WSS-626 changed the implementation of the SignatureUtils#getInclusivePrefixes method
to use a Set instead of a List. This change makes sense, however it changes the order that
the prefixes had historically been returned by this method. A client of ours is having a problem
with the new ordering. Although this is certainly a bug on their end, it seems reasonable
to replicate the previous behavior of this method as closely as possible while still fixing
the bug reported in the issue.
> I'd like to suggest using a LinkedHashSet instead of a TreeSet as the Set implementation
in this method. The LHS preserves the insertion order as the order the elements are returned
in. This should make this method behave as closely as possible prior to the 2.2.2 release
of WSS4J.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message