Wires.reset does not perform as expected for marshals with fields of Bytes

[RobAustin]

see net.openhft.chronicle.wire.WiresTest#test

 public static class Base {
        Bytes base = Bytes.elasticByteBuffer();
    }

    @Test
    public void test() {

        Base base1 = new Base();
        base1.base.clear().append("value1");

        Base base2 = new Base();
        base2.base.clear().append("value2");

        Wires.reset(base1);
        Wires.reset(base2);

        base1.base.clear().append("value1");

        Assert.assertEquals("", base2.base.toString());

    }

[epickrram]

I've committed a workaround for now to get the build passing.

bb34735

Unclear as to what the long-term solution should be, as the need to add an annotation is non-obvious, and garbage is generated on each reset() operation.

[peter-lawrey]

I agree. We should be able to do this eithout an annotation or creating garbage on each message. On 15 Jun. 2017 12:32, "Mark Price" <notifications@github.com> wrote: I've committed a workaround for now to get the build passing. bb34735 <bb34735> Unclear as to what the long-term solution should be, as the need to add an annotation is non-obvious, and garbage is generated on each reset() operation. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#45 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABBU8d_NKh-YASuSZTPZMlBjW2hAjcI3ks5sEQgzgaJpZM4N6Dx_> .

[epickrram]

Fixed for Bytes and StringBuilder - the cleanest solution to this may be documentation + allowing the user to register a custom FieldAccess handler in WireMarshaller.

[RobAustin]

@epickrram could you document this as you suggest and close this issue.

[RobAustin]

@epickrram could you pick this up today ? ( in other words add the documentation ) and close

[epickrram]

Will do...

[hft-team-city]

Released in Chronicle-Wire-2.20.101, BOM-2.20.134