Multipart handling not in-spec with Jakarta RESTful Web Services 3.1 using jakarta.ws.rs.FormParam

[ollelogdahl]

As far as I understand, multipart/form-data is not actually implemented according to the spec in regards to @jakarta.ws.rs.FormParam. The spec clearly states that the following should be valid:

@Path("widgets4")
public class WidgetsResource4 {

    @POST
    @Consumes(MediaType.MULTIPART_FORM_DATA)
    public Response postWidget(@FormParam("part1Name") String part1,
                               @FormParam("part2Name") InputStream part2,
                               @FormParam("part3Name") EntityPart part3) {...}
}

In the provided example, we have the following resource:

@POST
    @Path("/api/upload")
    @Consumes(MediaType.MULTIPART_FORM_DATA)
    public Response upload(@FormParam("part1") EntityPart part) {
        LOG.info("file: {}", part);
        return Response.ok().build();
    }

Which in Quarkus doesn't work. I have attached a minimal example where it doesn't work. Using the following test-command, we see that the part always get set to null. This is true no matter the type of part; String, which the docs say should work also doesn't.

curl -vvv -F "part1=hello" http://localhost:8080/api/upload

Is there a good reason why @FormParam support is not a feature and instead replaced using @RestForm in resteasy-reactive? I would like to report this as an issue but I assume some thought has been put into this.

[ollelogdahl]

I see we used the old resteasy 'classic', and the question is wrong- quarkus seems to handle it correctly. When updating to using quarkus-rest, it works with @FormParam String. Still, quarkus doesn't seem to register a converter for jakarta.ws.rs.core.EntityPart. Why isn't that implemented?

[ollelogdahl]

This should probably be reopened.