OpenAPI generation content-type mismatch

[cescoffier]

Describe the bug

Let's consider the following endpoint (using spring compatibility, but it should not matter):

    @GetMapping("/hello")
    public String hello() {
        return "hello world";
    }

The generated OpenAPI document has the following content:

---
openapi: 3.0.3
info:
  title: fortune-demo API
  version: 1.0.0-SNAPSHOT
paths:
  /hello:
    get:
      tags:
      - Hello Controller
      responses:
        "200":
          description: OK
          content:
            application/json:
              schema:
                type: string
components:
  securitySchemes:
    SecurityScheme:
      type: http
      description: Authentication
      scheme: basic

Two issues:

1. I didn't setup anything related to security - so why it's there?
2. the content type is wrong, it should be plain text in this case

(2) leads to be unable to use the Swagger UI as it gets a 405 HTTP response.

Expected behavior

It should provide the right content type and no security description.

Actual behavior

See description.

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[manofthepeace]

sorry for the ping; @MikeEdgar @phillip-kruger would be nice if that could be looked into. This issue is still present in quarkus 3.4.1

[phillip-kruger]

I think the default content type is json ? Or is this just for jaxrs? @geoand ?

[phillip-kruger]

I'll have a look at this a.s.a.p

[geoand]

It's json in Quarkus when the return type is a POJO (or similar)

[phillip-kruger]

Right, so the content type is correct even when using spring API we do this . The security is an issue though, I'll look at that

[phillip-kruger]

O wait, only when pojo, not string. So this is an issue? Might event be an issue in jaxrs?

[phillip-kruger]

This is also an issue for jax-rs. I am looking at a fix

[rsvoboda]

@cescoffier @phillip-kruger what about Uni<String>? Should it be treated as JSON or text?

[phillip-kruger]

Probably yes. Same for Optional I guess

[rsvoboda]

Probably yes

Yes for JSON?

[phillip-kruger]

Sorry, no I mean text.

[rsvoboda]

It's JSON now ... Will you create a PR to adjust that?

[phillip-kruger]

Yes I will.