New CoapRequest / CoapResponse Builder API feedback about java-coap

[sbernard31]

Not directly linked but I'm think that some part of the README was not updated with the new API :

-        // (optional) set custom observation relation store, for example one that will use external storage
+        // (optional) set custom observations store, for example one that will use external storage
-       .observationRelationsStore(new HashMapObservationRelations())
+       .observationsStore(new HashMapObservationsStore())

-// define subscription manager for observable resources
+// define observers manager for observable resources
-InboundSubscriptionManager subscriptionManager = new InboundSubscriptionManager();
+ObserversManager observersManager = new ObserversManager();

server = CoapServer.builder()
        // configure with plain text UDP transport, listening on port 5683
        .transport(new DatagramSocketTransport(5683))
        // define routing
        // (note that each resource function is a `Service` type and can be decorated/transformed with `Filter`)
        .route(RouterService.builder()
                .get("/.well-known/core", req ->
                        CoapResponse.ok("</sensors/temperature>", MediaTypes.CT_APPLICATION_LINK__FORMAT).toFuture()
                )
                .post("/actuators/switch", req -> {
                    // ...
                    return coapResponse(Code.C204_CHANGED).toFuture();
                })
                // observable resource
-               .get("/sensors/temperature", subscriptionManager.then(req ->
+               .get("/sensors/temperature", observersManager.then(req ->
-                        completedFuture(CoapResponse.ok("21C"))
+                        CoapResponse.ok("21C").toFuture())
                ))
        )
        .build();

observersManager.init(server);

I didn't test/execute the code, so probably deserve a double check 😅

[szysas]

Thanks for feedback. I agree than modifying transport context is really needed.
Thanks for spotting outdated readme. It is actually based on theses tests: https://github.com/open-coap/java-coap/blob/master/coap-core/src/test/java/protocolTests/UsageTest.java. Do you know any idea/tools how to verify if readme examples are up to date?

[sbernard31]

Do you know any idea/tools how to verify if readme examples are up to date?

I had some ideas but not sure they really works :

• I was thinking about using checkstyle with regexp ? (but probably not work)
• Using this github actions ? https://github.com/marketplace/actions/markdown-autodocs
• Using another supported language than markdown (e.g. reStructuredText or asciidoctor) which have include directive but it seems that github doesn't support it ...
• Using github code import but I understand you need to create permalink each time ... (and rendering is not so good)
  

  java-coap/coap-core/src/test/java/protocolTests/UsageTest.java

  Lines 64 to 88 in fa79e86

  	// define subscription manager for observable resources
  	ObserversManager observersManager = new ObserversManager();
  	server = CoapServer.builder()
  	// configure with plain text UDP transport, listening on port 5683
  	.transport(new DatagramSocketTransport(5683))
  	// define routing
  	// (note that each resource function is a `Service` type and can be decorated/transformed with `Filter`)
  	.route(RouterService.builder()
  	.get("/.well-known/core", req ->
  	CoapResponse.ok("</sensors/temperature>", MediaTypes.CT_APPLICATION_LINK__FORMAT).toFuture()
  	)
  	.post("/actuators/switch", req -> {
  	// ...
  	return coapResponse(Code.C204_CHANGED).toFuture();
  	})
  	// observable resource
  	.get("/sensors/temperature", observersManager.then(req ->
  	CoapResponse.ok("21C").toFuture()
  	))
  	)
  	.build();
  	observersManager.init(server);
  	server.start();

So nothing great 😬

[szysas]

I had some ideas but not sure they really works

Thanks