ratpack | collection of helpers for sinatra | Command Line Interface library

You can use TestHttpClient.params(action) to set request parameters. Something like this should do the trick:

The only thing I can think of is if you are attempting to import the Ratpack test classes in your main module, where they are not available (after all, they are test classes and are only available in the test module).

Just as a heads up, you are also using deprecated configurations. So unless you are in a legacy project with an old version, use these instead:

• testCompile -> testImplementation
• compile -> implementation
• runtime -> runtimeOnly

You can also get rid of the entire buildscript block and the apply plugin: "io.ratpack.ratpack-java" line, and just type:

You see HTTP/1.1 405 Method Not Allowed response status because your request gets handled by the get("product/:id") handler. If you want to use the same path for multiple HTTP methods, you can use prefix combined with byMethod method to define multiple handlers for the same path.

Consider the following example:

If you want to use multiple different HTTP methods for the same relative path, you still need to create such handlers using byMethod {} method. Otherwise, the first handler in the chain that matches the relative path handles the request, and it may fail or succeed. (In your case POST request fails with 405 Method Not Allowed because the get handler handles the request and it finds an incorrect HTTP method in the request. If you would like to see the GET request to fail instead of the POST one - reorder methods so the post {} is the first handler in the chain.)

This byMethod {} method allows to register multiple handlers for the same relative path, and those handlers will be resolved based on the request's HTTP method. In case of using prefix {} method you may access byMethod {} method in the path {} helper method:

In order for the backend application server https://example.com to generate 304 responses it will need to see the If-Modified-Since request header. In your case that header is getting to nginx but not to the application server. You need to tell nginx to pass it through. Add the following to your location block:

Got help on the Ratpack forum. I needed to bind it instead of add it.

long story short, rs.bodyToMono(String.class).defaultIfEmpty("") saved the day

Indeed, due to the upcoming modularisation of jOOQ 3.12, some split packages had to be renamed, namely the org.jooq.util package. In your manual setup, you need to change your imports from:

Is there any reason you keep your template files in src/main/thymeleaf? By default Thymeleaf templates should be stored in src/ratpack/thymeleaf directory.

ThymeleafModule class defines a folder name where all templates are stored. The default value is thymeleaf and when you create a shadowJar then you should find a folder thymeleaf right in the JAR archive. shadowJar copies src/ratpack/thymeleaf to this destination without any problem.

Java based Ratpack project is not aware of src/ratpack by default, but you can easily configure it by creating an empty file called .ratpack in src/ratpack and configuring server -> server.findBaseDir() (more detailed example below).

Here is a simple example:

build.gradle