如何从RoutingContext获取邮件正文？

Question

I created a vert.x HTTP server and I want to receive messages from clients in json format. This is my code:

public class HttpServerVerticle extends AbstractVerticle {
    @Override
    public void start(Future<Void> future) {
        Router router = Router.router(vertx)
            .exceptionHandler(ex -> log.error("Error: " + ex));
        router.route().handler(BodyHandler.create());
        router.route("/getData").handler(this::getRequestHandler);

        HttpServerOptions serverOptions = new HttpServerOptions();
        vertx.createHttpServer(serverOptions)
                .requestHandler(router::accept)
                .listen(9539, result -> {
                    if (result.succeeded()) {
                        future.complete();
                    } else {
                        future.fail(result.cause());
                    }
                });
    }

    private void getRequestHandler(RoutingContext request) {
        JsonObject data = request.getBodyAsJson();  // In this place I had exception
        ...
        request.response().end("{\"reply\":\"ok\"}");
    }
}

When my handler was fire and I get some message from the client I get this exception:

io.vertx.core.json.DecodeException: Failed to decode:Unexpected end-of-input: expected close marker for Object (start marker at [Source: (String)"{"ClientRequest":["ok"],"Type":"Test"[truncated 678 chars]; line: 1, column: 1])

How can I avoid this exception and all time get the full message?

Answer 1

You should specify the HTTP method

router.route("/getData").handler(this::getRequestHandler);

is expecting an HTTP GET, but what you need is an HTTP POST:

router.post("/getData")
  .consumes("application/json")
  .handler(this::getRequestHandler);

will accept json in the body. The consumes is optional and enforces the client to only send json.

I would also suggest to name the route "/data" instead of "/getData" to conform with the concept of RESTful APIs.

Answer 2

Its possible the client is not sending a valid json. This is a valid exception to handle in that case. For logging the request, you can simply use request.getBodyAsString() before doing getBodyAsJson()