[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wss4j-dev
Subject:    [jira] [Closed] (WSS-642) Use LinkedHashSet instead of TreeSet within getInclusivePrefixes
From:       "Colm O hEigeartaigh (JIRA)" <jira () apache ! org>
Date:       2019-04-04 14:57:00
Message-ID: JIRA.13211925.1548447898000.6853.1554389820389 () Atlassian ! JIRA
[Download RAW message or body]


     [ https://issues.apache.org/jira/browse/WSS-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Colm O hEigeartaigh closed WSS-642.
-----------------------------------

> Use LinkedHashSet instead of TreeSet within getInclusivePrefixes
> ----------------------------------------------------------------
> 
> Key: WSS-642
> URL: https://issues.apache.org/jira/browse/WSS-642
> 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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]