Incorrect link objects are implicitly sent on update about leshan HOT 5 CLOSED

You're right, since the refactoring/API changing all about object links (register, update, discover) is in a pretty bad state.
I currently work on it.

from leshan.

So, I fixed the problem of link object which does not contains instance ID at registration.
I also integrated what you propose to fix the update problem.
But, This means now when you want to update the Link Object part you must write something like that ...

client.send(new UpdateRequest(
         "registrationId", null, null, null, 
         LinkFormatHelper.getClientDescription(client.getObjectEnablers(), null)));

not really sexy !
Maybe, it's not so bad, because we should probably manage update automatically. User should not have to write this kind of code ...

from leshan.

Yes, may be we can improve this in the future...

from leshan.

The implementation of the visit method with UpdateRequest still contains this implementation:

LinkObject[] linkObjects = request.getObjectLinks();
if (linkObjects == null) 
coapRequest.setPayload(LinkObject.serialyse(linkObjects));

I think it should be implemented as described above

    if (linkObjects != null) {
        payload = LinkFormatUtils.payloadize(linkObjects);
        coapRequest.setPayload(payload);
    }

from leshan.

It was a bug. it should be fixed now.

from leshan.