On Mon, Oct 17, 2022 at 5:43 AM Ullrich Hafner
wrote:
> Shouldn’t XStream always pick the correct dynamic type (and not the static
> type) when serializing things?
>
As far as I know it does, but then again the representation for exotic
collection types is complex.
You should declare the
In one of my serialized instances I am using a TreeSet to store some
properties.
When I declare the Java field as SortedSet (interface) or TreeSet (class), the
Jenkins XStream correctly serializes the model. However, when I declare my
field as NavigableSet (interface), then the serialization
