Every generated request carries a RequestMeta object. You can inspect it before sending, or inside interceptors and callbacks, to understand how a call was built and how Domino REST will dispatch it.
@RequestFactory
public interface MoviesService {
@Path("library/movies/:movieName")
@GET
Movie getMovieByName(@PathParam("movieName") String movieName);
@Path("library/movies")
@GET
List<Movie> listMovies();
@Path("library/movies/:name")
@PUT
@SuccessCodes({200})
void updateMovie(@beanParam @RequestBody Movie movie);
}
All annotations on the resource method are captured as meta parameters, so you can introspect @Path, @GET, @Consumes, @Produces, and any others, alongside the values supplied by request arguments.
Meta-data includes the request and response types, HTTP method, full path (with path and matrix parameters applied), headers, query parameters, consumes/produces, and the full set of meta parameters derived from annotations and argument values. This makes it easy to log or adjust behavior based on the exact call shape.
MoviesServiceFactory.INSTANCE
.getMovieByName("hulk")
.onSuccess(movie ->{})
.send();